[Tinycc-devel] Re??Tinycc-devel Digest, Vol 180, Issue 1

[1657787678su]

help

------------------ Original ------------------

From: "tinycc-devel-request"<address@hidden>

Date: Mon, Apr 2, 2018 00:00 AM

To: "tinycc-devel"<address@hidden>;

Subject: Tinycc-devel Digest, Vol 180, Issue 1

Send Tinycc-devel mailing list submissions to
	address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.nongnu.org/mailman/listinfo/tinycc-devel
or, via email, send a message with subject or body 'help' to
	address@hidden

You can reach the person managing the list at
	address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinycc-devel digest..."


Today's Topics:

   1. Re: Integer promotion issue? (Michael Matz)
   2. Re: Some patches (Michael Matz)


----------------------------------------------------------------------

Message: 1
Date: Sat, 31 Mar 2018 21:53:47 +0200 (CEST)
From: Michael Matz <address@hidden>
To: address@hidden
Subject: Re: [Tinycc-devel] Integer promotion issue?
Message-ID: <address@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed

Hi,

On Sat, 31 Mar 2018, Patrick Pelissier wrote:

> when compiled with TCC GIT c41caac02d53373b296ccb179b730ada62137cc0
> produces the result on an linux/x86-64 platform:
>
> N=9223372036854775810
>
> whereas I was expecting
>
> N=2

Indeed.  Thanks for the report.  Fixed in mob (f0a25ca).


Ciao,
Michael.



------------------------------

Message: 2
Date: Sun, 1 Apr 2018 00:57:26 +0200 (CEST)
From: Michael Matz <address@hidden>
To: address@hidden
Subject: Re: [Tinycc-devel] Some patches
Message-ID: <address@hidden>
Content-Type: text/plain; charset=US-ASCII; format=flowed

Hi,

On Sat, 31 Mar 2018, Petr Skocik wrote:

> The first takes symlinks into account with header file caching (I need
> it with my build setup which uses a symlink in a weird way -- gcc and
> clang don't have problems with it but tcc did).

Can you clarify what the problem is exactly?  Thing is: realpath isn't 
available on WIN32, and using it causes many additional syscalls (per 
directory component for each tried include path).  If that's really 
necessary then it'd be better to just open the file in question and use 
the mount id and inode number as differentiator instead of the filename. 
But to understand that I'd like to know what "weird way" means in your 
build setup.

> The second fixes stringification with derived types. I noticed tcc
> stringified them wrong (like
> `void *(int)(int, void *(int))` where it should be `void (*(int, void
> (*)(int)))(int)`).

I've pushed this and amended it a bit (actually the above output misses 
another indirection, but that was a problem in _Generics handling of 
types), i.e. added a testcase.

> The last one makes tcc ignore static and restrict inside of []. C11
> allows these inside parameter declarations (with implications only on
> performance and compile-time checking), so I think tcc might as well
> silently accept them.

I've also pushed this, with slight changes (adding volatile handling, a 
testcase and formatting fixes).

> Thanks for considering the patches and thanks for the work on tcc.

And thank you for the contribution.


Ciao,
Michael.



------------------------------

Subject: Digest Footer

_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


------------------------------

End of Tinycc-devel Digest, Vol 180, Issue 1
********************************************