public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <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: Wed, 14 Oct 2009 07:48:00 -0000	[thread overview]
Message-ID: <20091014074837.17795.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41091-3639@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from mark at gcc dot gnu dot org  2009-10-14 07:48 -------
(In reply to comment #1)
> Actually, they have to have two different section types.
> 
> c::m()::TWO has to be in the comdat section for C::m().
> While c()::ONE does not and can be in a normal section.

INVALID? How is the user supposed to know (or care) about comdat? All they want
is make sure the constants get put in the same section. So how can one specify
that behavior for both ONE and TWO?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091


  parent reply	other threads:[~2009-10-14  7:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2009-10-17 11:28 ` mark at gcc dot gnu dot org
2010-08-11 23:52 ` roland at redhat dot com
     [not found] <bug-41091-4@http.gcc.gnu.org/bugzilla/>
2021-02-02 18:09 ` equinox-gccbugs at diac24 dot net
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

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=20091014074837.17795.qmail@sourceware.org \
    --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).