public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug objc/16546] [4.0 Regression] [unit-at-a-time] Solaris 10/x86 libobjc bootstrap failure: invalid assembler code Date: Tue, 28 Sep 2004 23:18:00 -0000 [thread overview] Message-ID: <20040928231808.26747.qmail@sourceware.org> (raw) In-Reply-To: <20040714171926.16546.ro@techfak.uni-bielefeld.de> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-09-28 23:18 ------- Patch here: <http://gcc.gnu.org/ml/gcc-patches/2004-09/msg02909.html>. -- What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16546
next prev parent reply other threads:[~2004-09-28 23:18 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-07-14 17:19 [Bug bootstrap/16546] New: " gcc-bugzilla at gcc dot gnu dot org 2004-07-14 17:25 ` [Bug bootstrap/16546] [3.5 Regression] " pinskia at gcc dot gnu dot org 2004-07-15 4:48 ` [Bug bootstrap/16546] [3.5 Regression] [unit-at-a-time] " pinskia at gcc dot gnu dot org 2004-07-15 19:52 ` ro at techfak dot uni-bielefeld dot de 2004-09-12 22:36 ` [Bug bootstrap/16546] [4.0 " pinskia at gcc dot gnu dot org 2004-09-13 9:39 ` ro at techfak dot uni-bielefeld dot de 2004-09-28 3:01 ` [Bug regression/16546] " pinskia at gcc dot gnu dot org 2004-09-28 3:24 ` pinskia at gcc dot gnu dot org 2004-09-28 3:30 ` [Bug objc/16546] " pinskia at gcc dot gnu dot org 2004-09-28 23:18 ` pinskia at gcc dot gnu dot org [this message] 2004-10-01 19:45 ` ro at techfak dot uni-bielefeld dot de 2004-10-06 3:44 ` pinskia at gcc dot gnu dot org 2004-10-28 16:16 ` ro at techfak dot uni-bielefeld dot de 2004-11-08 21:35 ` pinskia at gcc dot gnu dot org 2004-11-08 21:35 ` cvs-commit at gcc dot gnu dot org
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=20040928231808.26747.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).