[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2010-05-23 Thread ktietz at gcc dot gnu dot org
--- Comment #8 from ktietz at gcc dot gnu dot org 2010-05-23 07:41 --- As there is no feed-back for some time now. I've tested this issue with recent mingw runtimes and the issue is solved. As this isse is related to old pseudo-relocation and linker, and not related to gcc itself, I

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2010-04-05 Thread ktietz at gcc dot gnu dot org
--- Comment #7 from ktietz at gcc dot gnu dot org 2010-04-05 09:17 --- (In reply to comment #6) I added you to this thread, as you merged new pseudo-relocation code to mingw.org's runtime. As cygwin and mingw.org are supporting now new linker generated runtime-pseudo-relocation,

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2009-09-12 Thread ktietz at gcc dot gnu dot org
--- Comment #6 from ktietz at gcc dot gnu dot org 2009-09-12 10:55 --- I added you to this thread, as you merged new pseudo-relocation code to mingw.org's runtime. -- ktietz at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2009-09-04 Thread ktietz at gcc dot gnu dot org
--- Comment #5 from ktietz at gcc dot gnu dot org 2009-09-04 13:27 --- (In reply to comment #4) (In reply to comment #2) Is it possible that it triggers the exception trying to write in text.unlikely which is READONLY? Exactly. This is a linker, not a compiler issue.

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2009-07-30 Thread dannysmith at users dot sourceforge dot net
--- Comment #4 from dannysmith at users dot sourceforge dot net 2009-07-30 08:00 --- (In reply to comment #2) Is it possible that it triggers the exception trying to write in text.unlikely which is READONLY? Exactly. This is a linker, not a compiler issue. If you are using a

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2009-07-29 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2009-07-29 16:10 --- IIRC the cold attribute does a couple of things. The only thing I think that might cause this is putting it into a .text.cold section. -- pinskia at gcc dot gnu dot org changed: What|Removed

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2009-07-29 Thread ramiro dot polla at gmail dot com
--- Comment #2 from ramiro dot polla at gmail dot com 2009-07-30 03:43 --- I might be guessing wildly since I don't know that much about PE, but this is what more I've found: It crashes loading the dll in __pei386_runtime_relocator at address 65ec12a8: 65ec1290

[Bug target/40905] GCC creates invalid executable with auto-imported DLL and __attribute__((cold))

2009-07-29 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2009-07-30 03:59 --- Doesn't DLL source need to be compiled with -fPIC to allow it to work? So what is happening is you are getting a runtime relocation inside the .text.unlikely section which should not happen for DLLs I think ...