public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/92395] m68k-linux-gnu-gcc generates wrong code when the -mshort option is used
[not found] <bug-92395-4@http.gcc.gnu.org/bugzilla/>
@ 2020-04-21 20:00 ` eerott at gmail dot com
0 siblings, 0 replies; only message in thread
From: eerott at gmail dot com @ 2020-04-21 20:00 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92395
Eero Tamminen <eerott at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eerott at gmail dot com
--- Comment #10 from Eero Tamminen <eerott at gmail dot com> ---
> I think the option should just be removed at this point.
"-mshort" is still used with m68k gcc toolchain(s) that don't break it. Not to
build Linux binaries, but to cross-compile things where size matters.
It would be nice to be able to use (pre-built Debian) Linux m68k gcc to do such
cross-compilation.
Looking at https://gcc.gnu.org/git/?p=gcc.git;a=tree;f=gcc/config/m68k;hb=HEAD
"linux.h" and "netbsd-elf.h" headers use int & unsigned int for PTRDIFF &
SIZE_T, which produces broken code with -mshort, whereas "openbsd.h" and
"m68kemb.h" use "long int" & "long unsigned int" which work fine with and
without -mshort.
(I'm not sure whether I should be surprised that netbsd and openbsd work
differently. :-))
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-04-21 20:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-92395-4@http.gcc.gnu.org/bugzilla/>
2020-04-21 20:00 ` [Bug target/92395] m68k-linux-gnu-gcc generates wrong code when the -mshort option is used eerott at gmail dot com
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).