public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wouter.vermaelen at scarlet dot be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/49237] New: error with -flto:    'f' causes a section type conflict
Date: Mon, 30 May 2011 20:27:00 -0000	[thread overview]
Message-ID: <bug-49237-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: error with -flto:    'f' causes a section type
                    conflict
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: wouter.vermaelen@scarlet.be


> cat bug.cc
struct Bar;
struct Base1 {
        virtual ~Base1();
};
template<typename T> struct Base2 {
        virtual void f(T&) = 0;
};
template<typename> struct Foo : Base1, Base2<Bar> {
        virtual void f(Bar&) {}
};
template struct Foo<Bar>;


> g++-snapshot --version
g++-snapshot (GCC) 4.7.0 20110530 (experimental)

> g++-snapshot bug.cc -c -flto
> g++-snapshot bug.o -flto
In file included from bug.cc:8:0,
                 from :14:
bug.cc: In member function ‘f’:
bug.cc:9:15: error: f causes a section type conflict


Without the '-flto' option it works as expected.
This is on linux x86_64 (though I don't think this matters).


             reply	other threads:[~2011-05-30 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 20:27 wouter.vermaelen at scarlet dot be [this message]
2011-12-16  0:33 ` [Bug lto/49237] " pinskia at gcc dot gnu.org
2011-12-16 19:35 ` wouter.vermaelen at scarlet dot be
2011-12-31 23:14 ` pinskia 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-49237-4@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).