public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "equinox-gccbugs at diac24 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/41091] Using section attribute in c and c++ function causes section type conflict
Date: Tue, 02 Feb 2021 18:09:31 +0000 [thread overview]
Message-ID: <bug-41091-4-nsphreEERd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41091-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091
David L. <equinox-gccbugs at diac24 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |equinox-gccbugs at diac24 dot net
--- Comment #8 from David L. <equinox-gccbugs at diac24 dot net> ---
Issue persists in gcc 10.2, test program from comment #6 still errors out.
We're hitting this bug in production/real-world code [
https://github.com/FRRouting/frr/pull/6766 ]. What we're doing is very similar
to SystemTap's trace points, I believe those might be affected as well.
clang++ works fine meanwhile.
next parent reply other threads:[~2021-02-02 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41091-4@http.gcc.gnu.org/bugzilla/>
2021-02-02 18:09 ` equinox-gccbugs at diac24 dot net [this message]
2022-05-18 16:38 ` boreynol at microsoft dot com
2022-05-18 17:03 ` pinskia at gcc dot gnu.org
2024-05-21 16:09 ` paul_robinson at playstation dot sony.com
2009-08-17 13:58 [Bug c++/41091] New: " mark at gcc dot gnu dot org
2009-10-14 4:50 ` [Bug c++/41091] " pinskia at gcc dot gnu dot org
2009-10-14 7:48 ` mark at gcc dot gnu dot org
2009-10-17 11:28 ` mark at gcc dot gnu dot org
2010-08-11 23:52 ` roland at redhat dot com
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-41091-4-nsphreEERd@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).