> Am 15.07.2024 um 20:07 schrieb William Seurer via Gcc :
>
> On 7/12/24 7:47 AM, Richard Biener via Gcc wrote:
>> The first release candidate for GCC 11.5 is available from
>>
>> https://gcc.gnu.org/pub/gcc/snapshots/11.5.0-RC-20240712/
>>
>> and shortly its mirrors. It has been generated
On 7/12/24 7:47 AM, Richard Biener via Gcc wrote:
The first release candidate for GCC 11.5 is available from
https://gcc.gnu.org/pub/gcc/snapshots/11.5.0-RC-20240712/
and shortly its mirrors. It has been generated from git commit
r11-11573-g30ffca55041518.
I have so far bootstrapped and teste
Georg-Johann Lay writes:
> In a test case I see insn combine trying to match such
> expressions, which do not make any sense to me, like:
>
> Trying 2 -> 7:
> 2: r45:HI=r48:HI
>REG_DEAD r48:HI
> 7: {r47:HI=r45:HI|r46:PSI#0;clobber scratch;}
>REG_DEAD r46:PSI
>REG_
On Mon, 15 Jul 2024 at 14:16, U.Mutlu wrote:
>
> The below test code demonstrates that sscanf fails
> to parse the string "" (ie. an empty string inside "") in line2 (fErr=1).
> Is this a bug?
This mailing list is for discussing the development of GCC, and sscanf
is not part of GCC. The behaviour
The man page for sscanf on my machine indicates that [ "matches a
nonempty sequence of characters", so failing to match an empty
character sequence seems to be correct behavior.
On Mon, Jul 15, 2024 at 10:16 PM U.Mutlu wrote:
>
> The below test code demonstrates that sscanf fails
> to parse the s
The below test code demonstrates that sscanf fails
to parse the string "" (ie. an empty string inside "") in line2 (fErr=1).
Is this a bug?
Or is there maybe a workaround format string to be used with sscanf ?
/*
sscanf_bug_demo.cpp
sscanf fails scanning the string ""
Compile:
g++ -g -Wall -W
