public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10125: [3.2/3.3/3.4 regression] Infinite loop caused by -O2 Date: Sun, 23 Mar 2003 18:36:00 -0000 [thread overview] Message-ID: <20030323182600.8870.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10125; it has been noted by GNATS. From: Glen Nakamura <glen@imodulo.com> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, rth@gcc.gnu.org Cc: Subject: Re: optimization/10125: [3.2/3.3/3.4 regression] Infinite loop caused by -O2 Date: Sun, 23 Mar 2003 18:21:52 +0000 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10125 > State-Changed-From-To: analyzed->closed > State-Changed-By: rth > State-Changed-When: Sun Mar 23 02:57:36 2003 > State-Changed-Why: > Not a bug. Type-aliasing violation between "char **" and "unsigned **". Actually, the test case uses "signed char **" and "unsigned char **"... Not sure if that changes your analysis. - glen
next reply other threads:[~2003-03-23 18:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-23 18:36 Glen Nakamura [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-23 19:56 Richard Henderson 2003-03-23 2:57 rth 2003-03-22 9:56 Steven Bosscher 2003-03-22 4:57 bangerth
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=20030323182600.8870.qmail@sources.redhat.com \ --to=glen@imodulo.com \ --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).