https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116333
--- Comment #3 from Pali Rohár ---
Hello Andrew, have you checked if this is really duplicate?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116333
--- Comment #2 from Pali Rohár ---
Hello Andrew, you have wrote that this function is not optimized out because of
inlining. I tried to mark _winshowcmd() function with __attribute__((noinline))
but result is similar. Function _winshowcmd() is p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116334
Bug ID: 116334
Summary: LTO dllimport generates ureferenced symbol and unused
code
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116333
Bug ID: 116333
Summary: unused result of pure function is not optimized out
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
--- Comment #9 from Pali Rohár ---
(In reply to peter0x44 from comment #7)
> 5) windres --help has this list of "supported targets":
> x86_64-w64-mingw32-windres: supported targets: pe-x86-64 pei-x86-64
> pe-bigobj-x86-64 elf64-x86-64 pe-i386 pe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114449
--- Comment #3 from Pali Rohár ---
Note that clang optimizes it just with -O2 and does not require any special
pragma.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114449
--- Comment #2 from Pali Rohár ---
Interesting... I was expecting that some -O3 or better -Ofast option tells gcc
to optimize the code as much as possible.
I added that pragma before for-loop in the first example and then gcc really
optimized t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114449
Bug ID: 114449
Summary: bswap64 not optimized
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114448
Bug ID: 114448
Summary: Roundup not optimized
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
--- Comment #8 from Pali Rohár ---
Thank you for input, as you already figured out there is lot of work for this.
And I think I'm not skilled enough to implement everything properly, so I would
have to let this to gcc developers. I will answer q
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
--- Comment #5 from Pali Rohár ---
Thank you for info, I read that blog post and based on those details I adjusted
spec file
$ x86_64-w64-mingw32-gcc -dumpspecs > test.spec
by adding additional lines to test.spec:
.rc:
x86_64-w64-mingw32-wind
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109317
--- Comment #3 from Pali Rohár ---
Do you need some more input or test data about this issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
--- Comment #2 from Pali Rohár ---
Andrew, I do not know what is gcc driver nor what to do for it. But if you can
show me some pointers, I can try it.
Or if you need more details about files, usage, etc... please let me know.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108849
--- Comment #3 from Pali Rohár ---
Arsen, so based on my understooding (please correct me if I'm wrong), gcc's
"section" can be used on both code (functions) and data (global variables). And
ms's "code_seg" can be used only on code (functions).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
--- Comment #8 from Pali Rohár ---
Thanks for quick response and fixup of this issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
--- Comment #3 from Pali Rohár ---
For details, here is the compiler which produces the mentioned code:
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
Bug ID: 114319
Summary: htobe64-like function is not optimized on 32-bit x86
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108849
--- Comment #2 from Pali Rohár ---
`section` is the best option. MS says about it:
https://learn.microsoft.com/en-us/cpp/cpp/code-seg-declspec
> The code_seg declaration attribute names an executable text segment in the
> .obj file in which t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108851
Pali Rohár changed:
What|Removed |Added
See Also|https://sourceware.org/bugz |https://sourceware.org/bugz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108853
--- Comment #5 from Pali Rohár ---
Back to the original question. Can gcc add a new option -mcpu=e500 as alias to
-mcpu=8540 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108851
--- Comment #3 from Pali Rohár ---
Or do you have any other suggestions?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109317
--- Comment #2 from Pali Rohár ---
Any idea what can be done with this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109369
--- Comment #10 from Pali Rohár ---
> I would suggest to move the bug to the Binutils Bugzilla.
Done: https://sourceware.org/bugzilla/show_bug.cgi?id=30343
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109369
--- Comment #8 from Pali Rohár ---
So from the discussion, do I understand correctly that this is rather LD linker
issue?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108851
--- Comment #2 from Pali Rohár ---
So should I report this issue to binutils bugtracker then?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109369
--- Comment #4 from Pali Rohár ---
I wanted to point that marking _pei386_runtime_relocator() function with
__attribute__((used)) is working fine.
And whether _pei386_runtime_relocator() should participate in LTO at all? I
would rather ask, why
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109368
--- Comment #4 from Pali Rohár ---
Reported to binutils: https://sourceware.org/bugzilla/show_bug.cgi?id=30300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109368
--- Comment #2 from Pali Rohár ---
I do not know. The issue happens when LTO is enabled for GCC.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109369
Bug ID: 109369
Summary: LTO drops explicitly referenced symbol
_pei386_runtime_relocator
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109368
Bug ID: 109368
Summary: LTO drops entry point symbol
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Ass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109317
Bug ID: 109317
Summary: -Os generates bigger code than -O2 on 32-bit ARM
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108853
--- Comment #3 from Pali Rohár ---
I'm still using processors with e500 cores with recent Linux kernel versions
and I know also other people who also still using them.
Note that NXP still supports some QorIQ processors which have integrated e50
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108866
Bug ID: 108866
Summary: Allow to pass Windows resource file (.rc) as input to
gcc
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108849
Bug ID: 108849
Summary: __declspec(code_seg("segname")) does not work
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108853
Bug ID: 108853
Summary: Add new -mcpu=e500 alias for -mcpu=8540
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108852
Bug ID: 108852
Summary: Add gcc option for building NT kernel driver
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108851
Bug ID: 108851
Summary: gcc -pie generates unwanted PE export table
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
37 matches
Mail list logo