public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/54324] [4.8 Regression] GCC install document does not list minimum required g++ version Date: Tue, 18 Dec 2012 15:21:00 -0000 [thread overview] Message-ID: <bug-54324-4-LB1FvFKjF6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54324-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54324 --- Comment #9 from Aldy Hernandez <aldyh at gcc dot gnu.org> 2012-12-18 15:19:55 UTC --- Author: aldyh Date: Tue Dec 18 15:19:43 2012 New Revision: 194583 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=194583 Log: PR other/54324 * ansidecl.h (ATTRIBUTE_UNUSED): Do not set __attribute__ for GCC < 3.4. Modified: trunk/include/ChangeLog trunk/include/ansidecl.h
next prev parent reply other threads:[~2012-12-18 15:21 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-19 18:20 [Bug other/54324] New: GCC install document does not list minimum required g++ versions gary at intrepid dot com 2012-08-20 7:19 ` [Bug other/54324] [4.8 Regression] GCC install document does not list minimum required g++ version rguenth at gcc dot gnu.org 2012-09-19 14:38 ` rguenth at gcc dot gnu.org 2012-11-16 1:07 ` pinskia at gcc dot gnu.org 2012-12-10 18:11 ` aldyh at gcc dot gnu.org 2012-12-10 19:40 ` aldyh at gcc dot gnu.org 2012-12-11 10:13 ` rguenth at gcc dot gnu.org 2012-12-11 10:20 ` rguenth at gcc dot gnu.org 2012-12-11 10:21 ` rguenth at gcc dot gnu.org 2012-12-12 5:09 ` aldyh at gcc dot gnu.org 2012-12-12 10:57 ` redi at gcc dot gnu.org 2012-12-18 15:21 ` aldyh at gcc dot gnu.org [this message] 2012-12-18 15:28 ` aldyh at gcc dot gnu.org 2012-12-18 16:22 ` aldyh at gcc dot gnu.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-54324-4-LB1FvFKjF6@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).