Hi Andrew,
I see. Thanks for your speedy reply for clearing my confusion!
Have a great day!
Best regards,
Haoxin
Andrew Pinski 于2022年3月12日周六 12:33写道：
> On Fri, Mar 11, 2022 at 8:21 PM Haoxin Tu via Gcc wrote:
> >
> > Dear developers,
> >
> > May I seek your confirmation to check whether the
On Fri, Mar 11, 2022 at 8:21 PM Haoxin Tu via Gcc wrote:
>
> Dear developers,
>
> May I seek your confirmation to check whether the following program
> triggers a true wrong-code issue or not? I don't want to make noise to the
> bug repository so I'd like to seek your confirmation here first.
>
>
Dear developers,
May I seek your confirmation to check whether the following program
triggers a true wrong-code issue or not? I don't want to make noise to the
bug repository so I'd like to seek your confirmation here first.
The following case makes GCC outputs differ under -O1 below vs -O1 abov
Snapshot gcc-10-20220311 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20220311/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Note, this mailing list is for development of gcc, gcc-help
would be more appropriate.
On Fri, Mar 11, 2022 at 07:53:32PM +, Larry Jackson via Gcc wrote:
> I goofed and failed to put a space after the "case" word:
>
> switch(nu){
> case1: v1 =val;break;
> case2: v2 =val;break;
> case3: v3 =va
I goofed and failed to put a space after the "case" word:
switch(nu){
case1: v1 =val;break;
case2: v2 =val;break;
case3: v3 =val;break;
case4: v4 =val;break;
}
gcc compiler showed NO errors or warnings. Execution of the code produced
incorrect results.
After I added a space(no other changes), ev
