public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10021: [3.2/3.3/3.4 regression] [m68k] alias problem during loop pass Date: Tue, 08 Apr 2003 07:16:00 -0000 [thread overview] Message-ID: <20030408071600.23234.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10021; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, zippel@linux-m68k.org, gcc-prs@gcc.gnu.org, janis187@us.ibm.com Cc: Subject: Re: target/10021: [3.2/3.3/3.4 regression] [m68k] alias problem during loop pass Date: Tue, 08 Apr 2003 09:10:11 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10021 According to Zippel, this is an "alias problem during loop pass" The synopsis of PR 9745 says: [3.3/3.4 regression][powerpc] miscompiles libmcrypt (alias problem during loop) Could these PRs be related? Any ideas how to test that? Greetz Steven
reply other threads:[~2003-04-08 7:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030408071600.23234.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --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).