Snapshot gcc-13-20240531 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20240531/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> Am 31.05.2024 um 20:56 schrieb Georg-Johann Lay :
>
>
>
> Am 31.05.24 um 19:32 schrieb Richard Biener:
Am 31.05.2024 um 17:25 schrieb Paul Koning via Gcc :
>>>
>>>
>>>
On May 31, 2024, at 11:06 AM, Georg-Johann Lay wrote:
Am 31.05.24 um 17:00 schrieb P
Am 31.05.24 um 19:32 schrieb Richard Biener:
Am 31.05.2024 um 17:25 schrieb Paul Koning via Gcc :
On May 31, 2024, at 11:06 AM, Georg-Johann Lay wrote:
Am 31.05.24 um 17:00 schrieb Paul Koning:
On May 31, 2024, at 9:52 AM, Georg-Johann Lay wrote:
What's the recommended way to st
> Am 31.05.2024 um 17:25 schrieb Paul Koning via Gcc :
>
>
>
>> On May 31, 2024, at 11:06 AM, Georg-Johann Lay wrote:
>>
>>
>>
>> Am 31.05.24 um 17:00 schrieb Paul Koning:
> On May 31, 2024, at 9:52 AM, Georg-Johann Lay wrote:
>
> What's the recommended way to stop built-in
> On May 31, 2024, at 11:06 AM, Georg-Johann Lay wrote:
>
>
>
> Am 31.05.24 um 17:00 schrieb Paul Koning:
>>> On May 31, 2024, at 9:52 AM, Georg-Johann Lay wrote:
>>>
>>> What's the recommended way to stop built-in expansions in gcc?
>>>
>>> For example, avr-gcc expands isinff() to a bloa
Am 31.05.24 um 17:00 schrieb Paul Koning:
On May 31, 2024, at 9:52 AM, Georg-Johann Lay wrote:
What's the recommended way to stop built-in expansions in gcc?
For example, avr-gcc expands isinff() to a bloated version of an isinff()
implementation that's written in asm (PR115307).
Johan
> On May 31, 2024, at 9:52 AM, Georg-Johann Lay wrote:
>
> What's the recommended way to stop built-in expansions in gcc?
>
> For example, avr-gcc expands isinff() to a bloated version of an isinff()
> implementation that's written in asm (PR115307).
>
> Johann
Isn't that up to the target
On Fri, 31 May 2024 at 15:53, Georg-Johann Lay wrote:
>
>
>
> Am 31.05.24 um 15:56 schrieb Jonathan Wakely:
> > On Fri, 31 May 2024 at 14:52, Georg-Johann Lay wrote:
> >>
> >> What's the recommended way to stop built-in expansions in gcc?
> >>
> >> For example, avr-gcc expands isinff() to a bloat
Am 31.05.24 um 15:56 schrieb Jonathan Wakely:
On Fri, 31 May 2024 at 14:52, Georg-Johann Lay wrote:
What's the recommended way to stop built-in expansions in gcc?
For example, avr-gcc expands isinff() to a bloated version of an
isinff() implementation that's written in asm (PR115307).
Di
On Fri, 31 May 2024 at 14:52, Georg-Johann Lay wrote:
>
> What's the recommended way to stop built-in expansions in gcc?
>
> For example, avr-gcc expands isinff() to a bloated version of an
> isinff() implementation that's written in asm (PR115307).
Did you try -fno-builtin-isinff ?
What's the recommended way to stop built-in expansions in gcc?
For example, avr-gcc expands isinff() to a bloated version of an
isinff() implementation that's written in asm (PR115307).
Johann
Sorry to use another e-mail due to network issue.
I tried -fsection-anchors option. But it does not apply to the target.
Best regards
Clark Zhao
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
Thanks.
the UnixBench source code is as following:
unsigned long Run_Index;
Rec_Pointer Ptr_Glob,
Next_Ptr_Glob;
int Int_Glob;
Boolean Bool_Glob;
char Ch_1_Glob,
Ch_2_Glob;
int Arr_1_Glob [50];
int Arr_2_Glob [50] [50];
Boolean Reg = true;
long Begin_Time,
Sent from my iPhone
On Fri, May 31, 2024 at 4:59 AM Hanke Zhang via Gcc wrote:
>
> Hi,
> I've recently been trying to hand-write code to trigger automatic
> vectorization optimizations in GCC on Intel x86 machines (without
> using the interfaces in immintrin.h), but I'm running into a problem
> where I can't seem to
15 matches
Mail list logo
