public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ebotcazou@gcc.gnu.org To: ban@ipl.t.u-tokyo.ac.jp, ebotcazou@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org Subject: Re: c/9678: Incorrect specs for cpp_cpucommon on i386 Date: Thu, 20 Feb 2003 20:15:00 -0000 [thread overview] Message-ID: <20030220201502.4020.qmail@sources.redhat.com> (raw) Synopsis: Incorrect specs for cpp_cpucommon on i386 State-Changed-From-To: analyzed->closed State-Changed-By: ebotcazou State-Changed-When: Thu Feb 20 20:15:01 2003 State-Changed-Why: Fixed. Thanks for the patch! http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9678
next reply other threads:[~2003-02-20 20:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-20 20:15 ebotcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-20 8:44 ebotcazou 2003-02-12 21:56 BAN Nobuhiro
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=20030220201502.4020.qmail@sources.redhat.com \ --to=ebotcazou@gcc.gnu.org \ --cc=ban@ipl.t.u-tokyo.ac.jp \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@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).