public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jakub@gcc.gnu.org To: djohnson@osc.edu, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c++/6056: ICE on legal code with when optimizations higher that -O (ia64 only) Date: Tue, 26 Mar 2002 10:18:00 -0000 [thread overview] Message-ID: <20020326181850.15297.qmail@sources.redhat.com> (raw) Synopsis: ICE on legal code with when optimizations higher that -O (ia64 only) State-Changed-From-To: open->analyzed State-Changed-By: jakub State-Changed-When: Tue Mar 26 10:18:49 2002 State-Changed-Why: It is actually code with undefined behaviour (because it does invalid type punning), but no matter what gcc probably shouldn't ICE on it. Simplified into: extern unsigned long d[]; unsigned long foo (unsigned char *x, int y) { unsigned long a = 0, c = 0; unsigned short *e = (unsigned short *) &a; int i, b; for (i = 0; i < y; i++) c = (c << 1) ^ d[i & 3]; if (i & 3) a ^= c; a *= 1879048201; e[0] += e[1]; return a; } at -O2. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6056
next reply other threads:[~2002-03-26 18:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-26 10:18 jakub [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-26 1:26 djohnson
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020326181850.15297.qmail@sources.redhat.com \ --to=jakub@gcc.gnu.org \ --cc=djohnson@osc.edu \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).