Thank you Sirl,
>>-msvr4-struct-return=standard and -msvr4-struct-return=gnu (which would
be the default (-msvr4-struct-return=standard)
by default, you mean using registers to return?
Lokesh
On Fri, Nov 30, 2018 at 4:18 PM Franz Sirl
wrote:
>
> Am 2018-11-26 um 06:13 schrieb Lokesh Janghel:
> >
-- Forwarded message -
From: Siddhartha Sen
Date: Sat 1 Dec, 2018, 2:01 AM
Subject: Re: [GSOC] variations in testsuite results
To:
Hi Martin,
I apologise for the late reply.My semester end exams are
currently going on and I am finding it a bit difficult to devote
On 30.11.2018 20:12, Kees Cook wrote:
> On Fri, Nov 30, 2018 at 9:09 AM Kees Cook wrote:
>>
>> On Fri, Nov 30, 2018 at 5:20 AM Alexander Popov wrote:
>>>
>>> Currently the 'stackleak_cleanup' pass deleting a CALL insn is executed
>>> after the 'reload' pass. That allows gcc to do some weird optim
* Bill Schmidt:
> I don't think we have a real concern here. DD2.1 is used in a particular
> situation where GCC 4.8.5 is the supported compiler, and not used elsewhere.
> So I'd prefer not to cripple the compiler for this specific use case. If
> the customer with DD2.1 hardware chooses to use G
On Sun, 2 Dec 2018 at 04:45, nick wrote:
> My other question is related to the noexcept parts and that either I or
> you should move and CC the other involed list i.e. the llibstdc++ list.
Oh I didn't realise this thread wasn't already on that list. Yes, we
should be discussing it there, not here.
Sent offlist.
On Sun, 2 Dec 2018 at 20:06, nick wrote:
>
>
>
> On 2018-12-02 11:53 a.m., David Edelsohn wrote:
> > On Sat, Dec 1, 2018 at 11:46 PM nick wrote:
> >>
> >> On 2018-12-01 10:32 a.m., Jonathan Wakely wrote:
> >>> On Fri, 30 Nov 2018 at 20:54, Nicholas Krause wrote:
>
> This
On 12/3/18 8:34 AM, Florian Weimer wrote:
> * Aaron Sawdey:
>
>> If you are aware of any real world code that is faster when built
>> with -fno-builtin-strcmp and/or -fno-builtin-strncmp, please let me know
>> so I can look at avoiding those situations.
> Sorry, I have not tried to benchmark this.
* Aaron Sawdey:
> If you are aware of any real world code that is faster when built
> with -fno-builtin-strcmp and/or -fno-builtin-strncmp, please let me know
> so I can look at avoiding those situations.
Sorry, I have not tried to benchmark this.
One more question: There's a hardware erratum on
