Re: [Tinycc-devel] dwarf support

2022-05-06 Thread Ivo van Poorten
C'mon, you cannot put a bunch of #defines under a license. Just use whatever header file has the proper defines. On Fri, 6 May 2022 18:59:51 +0200 Herman ten Brugge via Tinycc-devel wrote: > I found another dwarf.h. Is this version OK? (See attachment) > >     Herman > > > On 5/6/22 17:28, Br

Re: [Tinycc-devel] dwarf support

2022-05-06 Thread Herman ten Brugge via Tinycc-devel
I found another dwarf.h. Is this version OK? (See attachment)     Herman On 5/6/22 17:28, Brian Callahan wrote: An FYI for packagers: dwarf.h is dual-licensed LGPLv3+ or GPLv2+. This is different than the rest of tcc which is LGPLv2+. ~Brian On 5/5/2022 5:13 AM, Herman ten Brugge via Tinycc-

Re: [Tinycc-devel] dwarf support

2022-05-06 Thread Brian Callahan
An FYI for packagers: dwarf.h is dual-licensed LGPLv3+ or GPLv2+. This is different than the rest of tcc which is LGPLv2+. ~Brian On 5/5/2022 5:13 AM, Herman ten Brugge via Tinycc-devel wrote: > The new gcc12 release does not support stabs any more. > This was a good reason to add support for dwa

Re: [Tinycc-devel] [patch] adding path resolution to #line directives

2022-05-06 Thread Michael Matz
Hey, On Fri, 6 May 2022, Raul Hernandez wrote: It would seem better to canonicalize during generating this, because the above and this don't look equivalent anyway (they are equivalent only when the above relative path is less that seven levels deep from /). In our case this isn’t an issue,

Re: [Tinycc-devel] [patch] adding path resolution to #line directives

2022-05-06 Thread Raul Hernandez
Hi, > It would seem better to canonicalize during generating this, because the > above and this don't look equivalent anyway (they are equivalent only when > the above relative path is less that seven levels deep from /). In our case this isn’t an issue, since the .c file is always compiled un