public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libffi/26048] [4.2/4.3/4.4 Regression] libffi doesn't build on Solaris 10/x86 with native assembler Date: Fri, 19 Dec 2008 14:11:00 -0000 [thread overview] Message-ID: <20081219140836.26771.qmail@sourceware.org> (raw) In-Reply-To: <bug-26048-81@http.gcc.gnu.org/bugzilla/> -- ro at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |ro at gcc dot gnu dot org |dot org | Status|NEW |ASSIGNED Last reconfirmed|2006-09-17 19:32:20 |2008-12-19 14:08:36 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26048
next prev parent reply other threads:[~2008-12-19 14:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-31 19:23 [Bug libffi/26048] New: " gcc-bugzilla at gcc dot gnu dot org 2006-02-01 1:09 ` [Bug libffi/26048] " ro at gcc dot gnu dot org 2006-02-01 1:19 ` [Bug libffi/26048] [4.1/4.2 Regression] " pinskia at gcc dot gnu dot org 2006-02-01 1:37 ` pinskia at gcc dot gnu dot org 2006-02-01 3:15 ` mmitchel at gcc dot gnu dot org 2006-02-01 10:17 ` jakub at gcc dot gnu dot org 2006-02-24 0:30 ` mmitchel at gcc dot gnu dot org 2006-05-25 2:40 ` mmitchel at gcc dot gnu dot org 2006-10-17 22:55 ` mmitchel at gcc dot gnu dot org 2007-02-14 10:04 ` [Bug libffi/26048] [4.1/4.2/4.3 " mmitchel at gcc dot gnu dot org 2008-07-04 20:19 ` [Bug libffi/26048] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-12-08 17:33 ` ro at techfak dot uni-bielefeld dot de 2008-12-19 14:11 ` ro at gcc dot gnu dot org [this message] 2008-12-19 15:02 ` ro at gcc dot gnu dot org 2008-12-19 15:05 ` ro at gcc dot gnu dot org 2010-04-28 21:03 ` ro 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=20081219140836.26771.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).