http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47071
Summary: Using -ffunction-sections produces bad assembler on my
testcase
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47071
--- Comment #2 from Aleksander Wabik 2010-12-27
20:24:44 UTC ---
Good to hear, now the QT team has a problem ;) Then, if I may ask: without
-ffunction-sections this code compiles fine, is such buggy assembler code
dangerous then? Or will it do wh
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: alex.wabik at gmail dot com
Target Milestone: ---
Created attachment 52579
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52579&action=edit
Testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104834
--- Comment #1 from Aleksander Wabik ---
Default visiblity symbols in the object file generated by the compilation:
- in GCC:
$ readelf -sW test.o | grep -v UND | grep -v SECTION | grep DEFAULT
1: 0 FILELOCAL DEF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104834
--- Comment #5 from Aleksander Wabik ---
(In reply to Andrew Pinski from comment #2)
> The enum issue is seperate from the vtable issue.
Should I create separate bug for that then?
