[Bug target/36834] structure return ABI for windows targets differs from native MSVC

2009-03-11 Thread mattias at virtutech dot se
--- Comment #5 from mattias at virtutech dot se 2009-03-11 12:42 --- (In reply to comment #4) >http://209.85.173.132/search?q=cache:e7XCjhLwHacJ:luabinaries.luaforge.net/manual.html+http://luabinaries.luaforge.net/manual.html%23LuaBinariesCompatible&hl=en&ct=clnk&cd

[Bug target/36834] structure return ABI for windows targets differs from native MSVC

2009-03-20 Thread mattias at virtutech dot se
--- Comment #7 from mattias at virtutech dot se 2009-03-20 17:16 --- The proposed patch works for plain C code, but also affects C++. Since libstdc++ contains code that returns aggregates or calls code that does, -mms-aggregate-return will make the generated code incompatible with the C

[Bug target/36834] structure return ABI for windows targets differs from native MSVC

2009-03-21 Thread mattias at virtutech dot se
--- Comment #9 from mattias at virtutech dot se 2009-03-21 16:45 --- Created an attachment (id=17508) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17508&action=view) Functions in libstdc++ returning aggregates > 8 bytes These are the functions in libstdc++ that c

[Bug target/36834] structure return ABI for windows targets differs from native MSVC

2009-03-21 Thread mattias at virtutech dot se
--- Comment #10 from mattias at virtutech dot se 2009-03-21 21:49 --- Note that C++ objects need not be larger than 8 bytes to qualify for returning on the stack (and thus subject to this cleanup problem). Any class with a copy constructor, for example, seems to be affected. Try

[Bug c/22485] New: pointer +- integer is never NULL

2005-07-14 Thread mattias at virtutech dot se
NULL Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mattias at virtutech dot se CC: gcc-bugs at

[Bug c/22485] pointer +- integer is never NULL

2005-07-14 Thread mattias at virtutech dot se
--- Additional Comments From mattias at virtutech dot se 2005-07-14 13:13 --- I forgot to state the version (4.0.0), but I have not seen any gcc version optimising this case. -- What|Removed |Added

[Bug c/22485] pointer +- integer is never NULL

2005-07-15 Thread mattias at virtutech dot se
--- Additional Comments From mattias at virtutech dot se 2005-07-15 09:12 --- It could be made an option so the user can tell GCC whether to make standard-conforming code go as fast as possible or if arithmetic on null pointers (as a gcc extension, say) is needed. -fnull-pointer-arith

[Bug c/22485] pointer +- integer is never NULL

2005-07-15 Thread mattias at virtutech dot se
--- Additional Comments From mattias at virtutech dot se 2005-07-15 15:29 --- (In reply to comment #18) > The "side" notes were written by people who know what they > intend. Therefore their inputs are completely relevant here. Even if you could show that these opt

[Bug target/36834] structure return ABI for windows targets differs from native MSVC

2008-07-18 Thread mattias at virtutech dot se
--- Comment #3 from mattias at virtutech dot se 2008-07-18 09:43 --- Thank you. Should the option be enabled by default on i686-pc-mingw32? Perhaps not, but it does make good on a previously broken ABI promise. The test case in that patch only covers the callee, not the caller. The

[Bug middle-end/4210] should not warning with dead code

2006-03-02 Thread mattias at virtutech dot se
--- Comment #17 from mattias at virtutech dot se 2006-03-02 09:22 --- We have resorted to case-by-case workarounds, usually a cast which would have been an identity operation had the condition been true. That is, if (sizeof x == 8) return x << 32 | x; would have its

[Bug c/26632] New: spurious warning: value computed is not used

2006-03-10 Thread mattias at virtutech dot se
: mattias at virtutech dot se GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26632

[Bug middle-end/26632] [4.1/4.2 Regression] spurious warning: value computed is not used

2006-03-10 Thread mattias at virtutech dot se
--- Comment #3 from mattias at virtutech dot se 2006-03-10 15:30 --- Yes, I realise it's the implicit integral conversion that causes the warning, but since the result is not used no matter what it seems wrong to warn for it - it cannot reasonably a sign of an error in the code. I

[Bug c/26634] New: spurious strtok_r warning with -Wwrite-strings

2006-03-10 Thread mattias at virtutech dot se
Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mattias at virtutech dot se GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-

[Bug c/21191] New: Bogus "control may reach end of non-void function" warning in inlined function

2005-04-24 Thread mattias at virtutech dot se
ssigned at gcc dot gnu dot org ReportedBy: mattias at virtutech dot se CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21191