public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/61848] [5 Regression] a previous declaration causes the section attribute to be lost
Date: Fri, 12 Sep 2014 14:57:00 -0000 [thread overview]
Message-ID: <bug-61848-4-wSV9fznde0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61848-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61848
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amodra at gmail dot com
--- Comment #10 from Alan Modra <amodra at gmail dot com> ---
Created attachment 33480
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33480&action=edit
A different approach to fixing this bug
I was playing with this one today, before I found your bugzilla Andrew. It has
been regression tested on x86_64, fixes the loss of section attributes, and
builds a 3.16 x86_64 defconfig kernel - haven't checked if it boots yet..
Adds a fix for C++ which has the same problem as C. (The s/olddecl/newdecl/
lines are because "if (TREE_CODE (newdecl) == FUNCTION_DECL) ... else switch
(TREE_CODE (olddecl))" looks horrible. Cosmetic really since we exit the
function before this code if TREE_CODE (newdecl) != TREE_CODE (olddecl).)
next prev parent reply other threads:[~2014-09-12 14:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 4:02 [Bug middle-end/61848] New: " pinskia at gcc dot gnu.org
2014-07-19 4:03 ` [Bug middle-end/61848] [4.10 Regression] " pinskia at gcc dot gnu.org
2014-07-19 5:49 ` pinskia at gcc dot gnu.org
2014-07-19 5:52 ` pinskia at gcc dot gnu.org
2014-07-19 6:01 ` pinskia at gcc dot gnu.org
2014-07-19 6:15 ` pinskia at gcc dot gnu.org
2014-07-19 6:20 ` pinskia at gcc dot gnu.org
2014-08-12 16:20 ` pinskia at gcc dot gnu.org
2014-09-03 6:39 ` [Bug middle-end/61848] [5 " ryabinin.a.a at gmail dot com
2014-09-11 1:14 ` pinskia at gcc dot gnu.org
2014-09-12 14:57 ` amodra at gmail dot com [this message]
2014-09-12 23:26 ` amodra at gmail dot com
2014-09-12 23:44 ` amodra at gmail dot com
2014-09-18 16:49 ` sasha.levin at oracle dot com
2014-09-23 15:18 ` pinskia at gcc dot gnu.org
2014-09-26 14:58 ` andi-gcc at firstfloor dot org
2014-09-28 18:00 ` andi-gcc at firstfloor dot org
2014-09-28 18:12 ` pinskia at gcc dot gnu.org
2014-09-28 18:14 ` trippels at gcc dot gnu.org
2014-09-28 18:18 ` trippels at gcc dot gnu.org
2014-09-28 18:30 ` andi-gcc at firstfloor dot org
2014-10-16 4:52 ` amodra at gmail dot com
2014-10-17 5:10 ` trippels at gcc dot gnu.org
2014-10-17 5:23 ` trippels 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-61848-4-wSV9fznde0@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: link
Be 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).