[Bug driver/52556] New: Ability to change GLIBC_DYNAMIC_LINKER

2012-03-11 Thread christer.solskogen at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52556 Bug #: 52556 Summary: Ability to change GLIBC_DYNAMIC_LINKER Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: enhancement Prio

[Bug driver/52556] Ability to change GLIBC_DYNAMIC_LINKER

2012-03-11 Thread christer.solskogen at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52556 --- Comment #1 from Christer Solskogen 2012-03-11 12:54:45 UTC --- I see now that the google gcc branch is having this kind of ability. Any plans of integrating them?

[Bug driver/52556] Ability to change GLIBC_DYNAMIC_LINKER

2012-03-11 Thread christer.solskogen at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52556 --- Comment #3 from Christer Solskogen 2012-03-11 15:50:57 UTC --- I could, but is not a sexy(*) as --with-runtime-root-prefix :-) *) http://patchwork.ozlabs.org/patch/80538/

[Bug lto/97637] New: Compiling with LTO causes a bigger binary

2020-10-30 Thread christer.solskogen at gmail dot com via Gcc-bugs
Assignee: unassigned at gcc dot gnu.org Reporter: christer.solskogen at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- I've been experimenting with amiberry (https://github.com/midwan/amiberry/tree/dev) a Amiga emulator to compile it wit

[Bug lto/97637] Compiling with LTO causes a bigger binary

2020-10-30 Thread christer.solskogen at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637 --- Comment #2 from Christer Solskogen --- You are correct. I've replaced Ofast with O2 (but it doesn't seem to matter that much) - with the default inline-unit-growth the binary gets 5% bigger. With inline-unit-growth=20 the binary gets 5%~ sma

[Bug lto/97637] Compiling with LTO causes a bigger binary

2020-10-30 Thread christer.solskogen at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637 --- Comment #4 from Christer Solskogen --- Okay, so LTO together with O2/O3 or Ofast will not help code size that much. I was worried that something was wrong with how GCC was configured or the command line parameters I was using since the binar

[Bug lto/97637] Compiling with LTO causes a bigger binary

2023-02-13 Thread christer.solskogen at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97637 Christer Solskogen changed: What|Removed |Added Resolution|--- |INVALID Status|WAITING

[Bug libcc1/67590] libcc1 cannot find objdump when cross build native

2023-02-13 Thread christer.solskogen at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67590 Christer Solskogen changed: What|Removed |Added CC||christer.solskogen at gmail dot co