public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <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: Sun, 28 Sep 2014 18:14:00 -0000 [thread overview]
Message-ID: <bug-61848-4-BLuZaIEkYd@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
Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|patch |
URL|https://gcc.gnu.org/ml/gcc- |
|patches/2014-09/msg01146.ht |
|ml |
Assignee|amodra at gcc dot gnu.org |pinskia at gcc dot gnu.org
--- Comment #18 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Andi Kleen from comment #16)
> Can Alan's patch be submitted please?
>
> I always need to apply it now before compiling a kernel.
See deadlocked discussion:
http://thread.gmane.org/gmane.comp.gcc.patches/321758/
Here's a testcase suitable for both C++ and C:
/* { dg-do compile } */
/* { dg-require-effective-target named_sections } */
/* { dg-final { scan-assembler "mysection" } } */
extern char foo;
char foo __attribute__ ((__section__(".mysection")));
next prev parent reply other threads:[~2014-09-28 18:14 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
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 [this message]
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-BLuZaIEkYd@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).