Snapshot gcc-6-20160207 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160207/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
On Wed, 3 Feb 2016, Keith Lindsay wrote:
> https://gcc.gnu.org/ml/gcc/current/
> currently redirects to
> https://gcc.gnu.org/ml/gcc/2016-01/
> instead of
> https://gcc.gnu.org/ml/gcc/2016-02/
Thanks for the report, Keith. This appears fixed now.
I also verified this for a couple of other mailin
Hi!
Building current GCC on gcc21.fsffrance.org fails, see build
http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=490729:
(`make all-gcc' build log at
http://toolchain.lug-owl.de/buildbot/deliver_artifact.php?mode=view&id=4541729)
g++ -fno-PIE -c -g -O2 -DIN_GCC -DCROSS_DIRECT
On Sun, Feb 7, 2016 at 12:48 PM, Florian Weimer wrote:
> * H. J. Lu:
>
>>> I tested GCC 5.3.1 and Clang 3.5.0.
>>>
>>> GCC Clang
>>> s0 non-emptynon-empty
>>> s1 non-emptyempty
>>> s2 non-emptyempty
>>> s3 emptyempty
>>> s4 emptyempty
>>> s5 no
* H. J. Lu:
>> I tested GCC 5.3.1 and Clang 3.5.0.
>>
>> GCC Clang
>> s0 non-emptynon-empty
>> s1 non-emptyempty
>> s2 non-emptyempty
>> s3 emptyempty
>> s4 emptyempty
>> s5 non-emptyempty
>>
>> I believe s3, s4, s5 are non-empty according
On Sun, Feb 7, 2016 at 12:08 PM, Florian Weimer wrote:
> * H. J. Lu:
>
>>> Any syntactical array argument (at the C level) is should be passed as
>>> a pointer. The language appears to change that.
>>
>> I didn't use aggregate so that array is excluded here.
>>
>>> For 2., static members and non-
* H. J. Lu:
>> Any syntactical array argument (at the C level) is should be passed as
>> a pointer. The language appears to change that.
>
> I didn't use aggregate so that array is excluded here.
>
>> For 2., static members and non-data members do not count.
>
> They do count here. That is why I
On Sun, Feb 7, 2016 at 11:36 AM, H.J. Lu wrote:
> On Sun, Feb 7, 2016 at 11:31 AM, Florian Weimer wrote:
>> * H. J. Lu:
>>
>>> I am proposing to update Intel386, x86-64 and IA MCU psABIs to specify
>>> how to pass/return empty struct:
>>>
>>> 1. "collection". A collection is a structure, union o
On Sun, Feb 7, 2016 at 11:31 AM, Florian Weimer wrote:
> * H. J. Lu:
>
>> I am proposing to update Intel386, x86-64 and IA MCU psABIs to specify
>> how to pass/return empty struct:
>>
>> 1. "collection". A collection is a structure, union or C++ class.
>> 2. "empty collection". An empty collecti
* H. J. Lu:
> I am proposing to update Intel386, x86-64 and IA MCU psABIs to specify
> how to pass/return empty struct:
>
> 1. "collection". A collection is a structure, union or C++ class.
> 2. "empty collection". An empty collection is:
>a. A collection without member. Or
>b. A collec
Empty struct value is passed differently in C and C++ on Intel386 and x86-64.
Different compilers use different calling conventions on the same platform:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60336
The same compiler behaves different on different platforms:
https://llvm.org/bugs/show_bug.
11 matches
Mail list logo
