public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: paolo@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hiten@uk.FreeBSD.org, nobody@gcc.gnu.org, paolo@gcc.gnu.org Subject: Re: c/8282: GCC 3.1 crashes under bitshift operations Date: Sat, 19 Oct 2002 02:49:00 -0000 [thread overview] Message-ID: <20021019094914.24602.qmail@sources.redhat.com> (raw) Synopsis: GCC 3.1 crashes under bitshift operations Responsible-Changed-From-To: unassigned->paolo Responsible-Changed-By: paolo Responsible-Changed-When: Sat Oct 19 02:49:13 2002 Responsible-Changed-Why: . State-Changed-From-To: open->feedback State-Changed-By: paolo State-Changed-When: Sat Oct 19 02:49:13 2002 State-Changed-Why: Hi. Could you please follow the detailed bug reporting instructions: http://gcc.gnu.org/bugs.html#detailed ?? In particular, could you please provide the self-contained preprocessed *.i file generated by adding -save-temps to your command line?? Thanks, Paolo. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8282
next reply other threads:[~2002-10-19 9:49 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-19 2:49 paolo [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-06 19:17 ebotcazou 2002-10-18 19:26 hiten
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=20021019094914.24602.qmail@sources.redhat.com \ --to=paolo@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=hiten@uk.FreeBSD.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).