public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mrs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/19162] [4.0 regression] ICE while building libobjc's sendmsg.c Date: Fri, 14 Jan 2011 22:30:00 -0000 [thread overview] Message-ID: <bug-19162-4-kAoDbhIaPc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19162-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19162 --- Comment #15 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2011-01-14 21:50:17 UTC --- Author: mrs Date: Fri Jan 14 21:50:11 2011 New Revision: 168824 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168824 Log: PR 19162 * objc-act.c (generate_struct_by_value_array): Do not output a definition for struct_forward_array. Modified: trunk/gcc/objc/ChangeLog
next parent reply other threads:[~2011-01-14 21:50 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19162-4@http.gcc.gnu.org/bugzilla/> 2011-01-14 22:30 ` mrs at gcc dot gnu.org [this message] 2004-12-26 21:27 [Bug target/19162] New: " debian-gcc at lists dot debian dot org 2004-12-26 21:27 ` [Bug target/19162] " debian-gcc at lists dot debian dot org 2004-12-26 21:28 ` debian-gcc at lists dot debian dot org 2004-12-26 21:36 ` pinskia at gcc dot gnu dot org 2004-12-26 22:19 ` pinskia at gcc dot gnu dot org 2004-12-26 22:21 ` pinskia at gcc dot gnu dot org 2004-12-26 22:26 ` pinskia at gcc dot gnu dot org 2004-12-26 22:47 ` pinskia at gcc dot gnu dot org 2004-12-27 0:18 ` pinskia at gcc dot gnu dot org 2004-12-28 6:31 ` debian-gcc at lists dot debian dot org 2004-12-28 14:47 ` pinskia at gcc dot gnu dot org 2005-01-04 1:37 ` pinskia at gcc dot gnu dot org 2005-01-04 1:47 ` pinskia at gcc dot gnu dot org 2005-02-17 8:46 ` cvs-commit at gcc dot gnu dot org 2005-02-17 8:51 ` rearnsha 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=bug-19162-4-kAoDbhIaPc@http.gcc.gnu.org/bugzilla/ \ --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).