On Sunday, 16 May 2021 at 00:00:30 UTC, Walter Bright wrote:
> So, I propose that once ImportC is ready, that persons familiar with those code bases try out the SQLite and Lua projects. Failures should be reduced to minimal test cases for incorporation into the ImportC test suite.

If you think it would be helpful I'll try building our in-house C
libraries since I understand those and submit any cases that fail.
I imagine quite a few people are going to be intrigued by this
project (as a new C compiler doesn't come around every day) and
will try building most of their C projects/dependencies.

I'm not sure if this is applicable, but we still have some sun/
sparc machines around in case building on a big endian environment
would provide you with useful data.  Sparc cores are still burned
into quite a few FPGAs.

The test suite should build up quickly.  Getting rid of duplicate
tests may turn out to be an issue.

On 5/16/2021 1:51 AM, Chris Piker wrote:
> If you think it would be helpful I'll try building our in-house C
> libraries since I understand those and submit any cases that fail.
> I imagine quite a few people are going to be intrigued by this
> project (as a new C compiler doesn't come around every day) and
> will try building most of their C projects/dependencies.
> 
> I'm not sure if this is applicable, but we still have some sun/
> sparc machines around in case building on a big endian environment
> would provide you with useful data.  Sparc cores are still burned
> into quite a few FPGAs.
> 
> The test suite should build up quickly.  Getting rid of duplicate
> tests may turn out to be an issue.

That would be welcome. But I'd suggest waiting a bit. There's plenty of known problems with it at the moment, so you'd be wasting your valuable time dealing with that.

Wait until it's doing better.

On Sunday, 16 May 2021 at 00:00:30 UTC, Walter Bright wrote:

> So, I propose that once ImportC is ready, that persons familiar with those code bases try out the SQLite and Lua projects. Failures should be reduced to minimal test cases for incorporation into the ImportC test suite.

I think that if this feature is going to added, then it makes sense to ensure that a test suite is present to prove its correctness. Users should not be expected to pay for wrong implementation. Perhaps the MIR C test suite I referred to earlier can be used to validate the implementation; I think it has good coverage of standard C and the tests are also small.

I am familiar with Lua but I would only consider spending any effort after I am convinced this feature has a proper testsuite. Otherwise as you mention in another thread, it just wastes time.

On 5/16/2021 3:51 AM, Dibyendu Majumdar wrote:
> I think that if this feature is going to added, then it makes sense to ensure that a test suite is present to prove its correctness. Users should not be expected to pay for wrong implementation. Perhaps the MIR C test suite I referred to earlier can be used to validate the implementation; I think it has good coverage of standard C and the tests are also small.

The Mir suite does look usable and good. I'm a bit concerned about the license for it, as I'd like to install the test suite on github.

On Sunday, 16 May 2021 at 19:12:26 UTC, Walter Bright wrote:
> On 5/16/2021 3:51 AM, Dibyendu Majumdar wrote:
>> I think that if this feature is going to added, then it makes sense to ensure that a test suite is present to prove its correctness. Users should not be expected to pay for wrong implementation. Perhaps the MIR C test suite I referred to earlier can be used to validate the implementation; I think it has good coverage of standard C and the tests are also small.
>
> The Mir suite does look usable and good. I'm a bit concerned about the license for it, as I'd like to install the test suite on github.

Yes, the tests are sourced from various places, and some are GPL. I suppose it can be put into a standalone test repo so as not to contaminate D license with GPL.

On Sunday, 9 May 2021 at 20:57:06 UTC, Walter Bright wrote:
> https://github.com/dlang/dmd/pull/12507
>
> If you could add a C compiler to dmd with 3000 lines of code, so C code could be imported directly? I would!

importC has been added as a keyword to bugzilla, please monitor it as any bugs are critical to be fixed before first release.

https://issues.dlang.org/buglist.cgi?keywords=importC