public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug lto/49237] New: error with -flto:    'f' causes a section type conflict
@ 2011-05-30 20:27 wouter.vermaelen at scarlet dot be
  2011-12-16  0:33 ` [Bug lto/49237] " pinskia at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: wouter.vermaelen at scarlet dot be @ 2011-05-30 20:27 UTC (permalink / raw)
  To: gcc-bugs

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).


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-12-31 23:08 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-05-30 20:27 [Bug lto/49237] New: error with -flto: 'f' causes a section type conflict wouter.vermaelen at scarlet dot be
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

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).