[Bug ld/32871] New: ld/ldmain.c#L425 incorrect location of #endif

2025-04-14 Thread euloanty at live dot com
Component: ld Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- https://github.com/bminor/binutils-gdb/blob/6ef74a3985befe3cb07a64d089ff00694f4674dd/ld/ldmain.c#L425 i think timeradd (& pd->use.ru_stime, &

[Bug ld/32871] ld/ldmain.c#L425 incorrect location of #endif

2025-04-14 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32871 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com

[Bug binutils/32466] nrun build error

2024-12-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32466 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com

[Bug binutils/32466] New: nrun build error

2024-12-16 Thread euloanty at live dot com
Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- /home/cqwrteur/toolchains_build/binutils-gdb/sim/common/nrun.c:150:23: error: assignment to 'void (*)(void)' from incompatible pointer type '__sighandler_t'

[Bug binutils/32457] New: multiple build issues with windows host

2024-12-13 Thread euloanty at live dot com
Component: binutils Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- /home/cqwrteur/toolchains_build/binutils-gdb/readline/readline/terminal.c:803:7: error: too many arguments to function 'tputs' 803 | tputs (_rl_

[Bug binutils/32250] New: ppc/hw_sem.c does not build for x86_64-w64-mingw32 host

2024-10-07 Thread euloanty at live dot com
Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- Windows has no sys/ipc.h and i use --enable-targets=all to build all targets for binutils. The don't work. /home

[Bug binutils/32250] ppc/hw_sem.c does not build for x86_64-w64-mingw32 host

2024-10-07 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32250 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com

[Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro

2024-10-06 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32243 --- Comment #1 from cqwrteur --- Created attachment 15732 --> https://sourceware.org/bugzilla/attachment.cgi?id=15732&action=edit patch -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/32244] strip should deal with all architectures

2024-10-06 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=32244 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com -- You are

[Bug binutils/32244] New: strip should deal with all architectures

2024-10-06 Thread euloanty at live dot com
Component: binutils Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- It is so frustrating that strip is not cross platform. A lot of GCC and binutils have issues with make install-strip. I have to use llvm-strip instead. Any

[Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro

2024-10-06 Thread euloanty at live dot com
||euloanty at live dot com -- You are receiving this mail because: You are on the CC list for the bug.

[Bug binutils/32243] New: NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro

2024-10-06 Thread euloanty at live dot com
Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- /home/csrg/toolchains_build/binutils-gdb/binutils/dlltool.c: In function 'main': /home/csrg/toolch

[Bug gold/32198] New: unsupported target loongarch64-unknown-elf

2024-09-22 Thread euloanty at live dot com
Component: gold Assignee: ccoutant at gmail dot com Reporter: euloanty at live dot com CC: ian at airs dot com Target Milestone: --- checking for library containing dlsym... none required configure: error: "unsupported target loongarch64-unknown-elf&qu

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 cqwrteur changed: What|Removed |Added Attachment #15606|0 |1 is obsolete|

[Bug ld/31962] In function 'gldelf_x86_64_get_script':

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31962 cqwrteur changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #25 from cqwrteur --- Created attachment 15608 --> https://sourceware.org/bugzilla/attachment.cgi?id=15608&action=edit just exclude all things here -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31962] In function 'gldelf_x86_64_get_script':

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31962 --- Comment #3 from cqwrteur --- ; else if (bfd_link_pie (&link_info) && link_info.separate_code) return ; else if (bfd_link_pie (&link_info)) return are you kidding me? -- You are receiving this mail because: You are on th

[Bug ld/31962] In function 'gldelf_x86_64_get_script':

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31962 --- Comment #2 from cqwrteur --- Created attachment 15607 --> https://sourceware.org/bugzilla/attachment.cgi?id=15607&action=edit what's going on here? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31962] In function 'gldelf_x86_64_get_script':

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31962 --- Comment #1 from cqwrteur --- looks like a musl only issue. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31962] In function 'gldelf_x86_64_get_script':

2024-07-08 Thread euloanty at live dot com
||euloanty at live dot com Host||x86_64-linux-musl Build||x86_64-pc-linux-gnu -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/31962] New: In function 'gldelf_x86_64_get_script':

2024-07-08 Thread euloanty at live dot com
iority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- eelf_x86_64.c: In function 'gldelf_x86_64_get_script': eelf_x86_64.c:2692:42: error: 'return' with no value, in function returning non-

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #24 from cqwrteur --- /home/cqwrteur/toolchains_build/binutils-gdb/gprofng/src/Experiment.cc:234:12: error: 'fopen64' was not declared in this scope; did you mean 'open64'? 234 | fh = fopen64 (fname, NTXT ("r")); |

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #23 from cqwrteur --- (In reply to cqwrteur from comment #22) > (In reply to Sam James from comment #15) > > See gprofng/configure.ac:175 which sets _MUSL_LIBC. > > it does not really work out. a lot of things are not defined like

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #22 from cqwrteur --- (In reply to Sam James from comment #15) > See gprofng/configure.ac:175 which sets _MUSL_LIBC. it does not really work out. a lot of things are not defined like fopen64, fstat64. you really should not use the

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #21 from cqwrteur --- /home/cqwrteur/toolchains_build/binutils-gdb/gprofng/src/../../include/libiberty.h:112:14: error: conflicting declaration of C function 'char* basename(const char*)' 112 | extern char *basename (const char *

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #20 from cqwrteur --- eelf_x86_64.c: In function 'gldelf_x86_64_get_script': eelf_x86_64.c:2692:42: error: 'return' with no value, in function returning non-void [-Wreturn-mismatch] 2692 | && link_info.separate_code)

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 cqwrteur changed: What|Removed |Added Attachment #15605|0 |1 is obsolete|

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #18 from cqwrteur --- (In reply to cqwrteur from comment #16) > (In reply to Sam James from comment #15) > > See gprofng/configure.ac:175 which sets _MUSL_LIBC. > > it does not set it for me. patch still not working out -- You

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #17 from cqwrteur --- Created attachment 15605 --> https://sourceware.org/bugzilla/attachment.cgi?id=15605&action=edit correct patch i have put a patch here. This is exactly the reason why musl libc is a crap. Everyone should j

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #16 from cqwrteur --- (In reply to Sam James from comment #15) > See gprofng/configure.ac:175 which sets _MUSL_LIBC. it does not set it for me. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #14 from cqwrteur --- (In reply to cqwrteur from comment #13) > (In reply to Sam James from comment #12) > > *** Bug 31960 has been marked as a duplicate of this bug. *** > > This patch is WRONG. > > > there is no __musl__ relat

[Bug gprofng/30779] gprofng: fails to build with musl-1.2.4 (gprofng/src/Data_window.h:56:3: error: 'off64_t' does not name a type; did you mean 'off_t'?)

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30779 --- Comment #13 from cqwrteur --- (In reply to Sam James from comment #12) > *** Bug 31960 has been marked as a duplicate of this bug. *** This patch is WRONG. there is no __musl__ related macros in musl libc. musl does not want you to dete

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 --- Comment #6 from cqwrteur --- (In reply to cqwrteur from comment #5) > (In reply to Sam James from comment #4) > > Dupe. > > > > *** This bug has been marked as a duplicate of bug 30779 *** > > what? it is not resolved for me why? i am u

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 cqwrteur changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 --- Comment #3 from cqwrteur --- /home/cqwrteur/toolchains_build/binutils-gdb/gprofng/libcollector/iotrace.c:3005:16: error: redefinition of 'fgetpos' 3005 | DCL_FGETPOS64 (fgetpos64) |^ /home/cqwrteur/toolchains

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 --- Comment #2 from cqwrteur --- Created attachment 15604 --> https://sourceware.org/bugzilla/attachment.cgi?id=15604&action=edit stderr failure -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 --- Comment #1 from cqwrteur --- Created attachment 15603 --> https://sourceware.org/bugzilla/attachment.cgi?id=15603&action=edit config -- You are receiving this mail because: You are on the CC list for the bug.

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com -- You are

[Bug gprofng/31960] musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31960 cqwrteur changed: What|Removed |Added Host||x86_64-linux-musl Target|

[Bug gprofng/31960] New: musl compilation failure: error: 'stat64' was not declared in this scope; did you mean 'fstat64'?

2024-07-08 Thread euloanty at live dot com
) Status: UNCONFIRMED Severity: normal Priority: P2 Component: gprofng Assignee: vladimir.mezentsev at oracle dot com Reporter: euloanty at live dot com Target Milestone: --- musl failure -- You are receiving this mail because: You ar

[Bug binutils/31930] Error: cannot represent relocation type BFD_RELOC_64 for x86_64-w64-mingw32 target

2024-07-08 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31930 cqwrteur changed: What|Removed |Added Resolution|--- |MOVED Status|UNCONFIRMED

[Bug binutils/31930] Error: cannot represent relocation type BFD_RELOC_64 for x86_64-w64-mingw32 target

2024-06-25 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31930 cqwrteur changed: What|Removed |Added Build||x86_64-pc-linux-gnu Host|

[Bug binutils/31930] Error: cannot represent relocation type BFD_RELOC_64 for x86_64-w64-mingw32 target

2024-06-25 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31930 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com

[Bug binutils/31930] New: Error: cannot represent relocation type BFD_RELOC_64

2024-06-25 Thread euloanty at live dot com
Component: binutils Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- /home/cqwrteur/toolchains/x86_64-pc-linux-gnu/x86_64-w64-mingw32/x86_64-w64-mingw32/bin/as: BFD (GNU Binutils) 2.42.50.20240626 assertion fail

[Bug gas/31796] Internal error in write_function_pdata at obj-coff-seh

2024-05-24 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31796 --- Comment #2 from cqwrteur --- I think the problem is caused by: https://github.com/bminor/binutils-gdb/blob/78726a8b7cbe45e6197169580ea304fc2ea647da/gas/config/obj-coff-seh.c#L927 This function may be wrong? -- You are receiving this ma

[Bug gas/31796] Internal error in write_function_pdata at obj-coff-seh

2024-05-24 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=31796 --- Comment #1 from cqwrteur --- Created attachment 15533 --> https://sourceware.org/bugzilla/attachment.cgi?id=15533&action=edit bugged asm $ aarch64-w64-mingw32-gcc -c a.s a.s: Assembler messages: a.s:19: Internal error in write_function_

[Bug gas/31796] Internal error in write_function_pdata at obj-coff-seh

2024-05-24 Thread euloanty at live dot com
||euloanty at live dot com Host||x86_64-pc-linux-gnu Target||aarch64-w64-mingw32 Version|unspecified |2.43 (HEAD) -- You are receiving this mail because: You are

[Bug gas/31796] New: Internal error in write_function_pdata at obj-coff-seh

2024-05-24 Thread euloanty at live dot com
Component: gas Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- aarch64-w64-mingw32-gcc -c a.c /tmp/ccBPN4vQ.s: Assembler messages: /tmp/ccBPN4vQ.s:19: Internal error in write_function_pdata at /home/cqwrteur

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking with ld

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #42 from cqwrteur --- *** Bug 30375 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #17 from cqwrteur --- Created attachment 14898 --> https://sourceware.org/bugzilla/attachment.cgi?id=14898&action=edit English translation -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #16 from cqwrteur --- Created attachment 14897 --> https://sourceware.org/bugzilla/attachment.cgi?id=14897&action=edit Someone has found the problem here Someone has found the problem here. std::cout does not bind correctly for

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #15 from cqwrteur --- Created attachment 14896 --> https://sourceware.org/bugzilla/attachment.cgi?id=14896&action=edit He found that ld binds std::cout to the address of std::cout in the dll Why is this .refptr?? It should be ju

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #14 from cqwrteur --- Some one tries this program: #include #include #include #include typedef void* (__cdecl* fn_type_t)(void* self, char const* string); int main() { MessageBoxA(nullptr,"pause",nullptr,0); a

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #13 from cqwrteur --- .text:000140001588 ; === S U B R O U T I N E === .text:000140001588 .text:000140001588 ;

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #12 from cqwrteur --- Ida pro result for GNU ld. I do not see jmp instruction here. .text:000140001540 ; === S U B R O U T I N E === .text:0001

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #11 from cqwrteur --- Here is the disassembly result from IDA pro. .text:000140001540 ; === S U B R O U T I N E === .text:000140001540 .text:000

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #10 from cqwrteur --- Created attachment 14895 --> https://sourceware.org/bugzilla/attachment.cgi?id=14895&action=edit ld no link -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #9 from cqwrteur --- Created attachment 14894 --> https://sourceware.org/bugzilla/attachment.cgi?id=14894&action=edit ld no link ld no link 1 -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #8 from cqwrteur --- Created attachment 14893 --> https://sourceware.org/bugzilla/attachment.cgi?id=14893&action=edit lld has link from text section that jmps here while ld does not lld has link from text section that jmps here

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added CC||jakub at redhat dot com -- You are receiv

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #7 from cqwrteur --- Created attachment 14892 --> https://sourceware.org/bugzilla/attachment.cgi?id=14892&action=edit executable -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #6 from cqwrteur --- Created attachment 14891 --> https://sourceware.org/bugzilla/attachment.cgi?id=14891&action=edit ld missing import of ios_base_library_init I use lld and it imports one more symbol than ld. I guess it is th

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added CC||amodra at gmail dot com -- You are receiv

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #5 from cqwrteur --- (In reply to Alan Modra from comment #1) > Does this problem still occur after my patch for pr30343? Please fix this asap. I have reported this for half a year and it is still unfixed. This breaks basically ev

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #3 from cqwrteur --- (In reply to cqwrteur from comment #2) > (In reply to Alan Modra from comment #1) > > Does this problem still occur after my patch for pr30343? > > Yes, it still occurs. Just crashing for hello world. 30375

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #4 from cqwrteur --- https://sourceware.org/bugzilla/show_bug.cgi?id=30375 -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-05-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 --- Comment #2 from cqwrteur --- (In reply to Alan Modra from comment #1) > Does this problem still occur after my patch for pr30343? Yes, it still occurs. Just crashing for hello world. -- You are receiving this mail because: You are on th

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking with ld

2023-05-07 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added CC||nickc at redhat dot com,

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking with ld

2023-04-21 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com -- You are

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking with ld

2023-04-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added Depends on||29973 Referenced Bugs: https://sourcewar

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-04-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 cqwrteur changed: What|Removed |Added Blocks||30375 Referenced Bugs: https://sourcewar

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking with ld

2023-04-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added Summary|C++ std::cout's rdbuf gives |C++ std::cout's rdbuf gives

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking

2023-04-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 --- Comment #1 from cqwrteur --- 6156746547736C54 is clearly not a possible address. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking

2023-04-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added Target||x86_64-w64-mingw32 -- You are receiving t

[Bug ld/30375] New: C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking

2023-04-20 Thread euloanty at live dot com
IRMED Severity: critical Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- struct foo { foo() { __builtin_puts("hello\n");

[Bug ld/30375] C++ std::cout's rdbuf gives ridiculous address on windows with dynamic linking

2023-04-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30375 cqwrteur changed: What|Removed |Added Priority|P2 |P1 -- You are receiving this mail because

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-04-01 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added CC||nickc at redhat dot com -- You are receiv

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-03-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added CC||euloanty at live dot com -- You are

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-03-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 cqwrteur changed: What|Removed |Added Resolution|--- |MOVED Status|ASSIGNED

[Bug ld/30254] iostream crashes with ld linker for windows targets

2023-03-20 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30254 cqwrteur changed: What|Removed |Added Priority|P2 |P1 Severity|normal

[Bug ld/30254] New: iostream crashes with ld linker for windows targets

2023-03-20 Thread euloanty at live dot com
Component: ld Assignee: unassigned at sourceware dot org Reporter: euloanty at live dot com Target Milestone: --- Bug issue 29973 was a mess. So I decided to start a new one and close bug 29973. GCC 13 made several changes to iostream, including making it with an

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-03-11 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #40 from cqwrteur --- (In reply to Nick Clifton from comment #32) > Hi, > > I am wondering if there are two problems here, rather than just one. So > please could you check a couple of things for me ? > > 1. Does iostream.ex

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-03-06 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #39 from cqwrteur --- (In reply to Nick Clifton from comment #14) > Well I have just tried x86_64-w64-mingw32-g++ from Fedora rawhide (which is > based on gcc version 12) and I still cannot reproduce the problem. So I am > beginni

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-23 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #38 from cqwrteur --- (In reply to Nick Clifton from comment #32) > Hi, > > I am wondering if there are two problems here, rather than just one. So > please could you check a couple of things for me ? > > 1. Does iostream.ex

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #37 from cqwrteur --- jwakely do you think it is caused by __init_priority__ ? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 cqwrteur changed: What|Removed |Added CC||jwakely.gcc at gmail dot com -- You are r

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #36 from cqwrteur --- https://github.com/gcc-mirror/gcc/commit/ec59848074ba8c4310cbadb603822bfaeff03a32 See this -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #35 from cqwrteur --- (In reply to Nick Clifton from comment #32) > Hi, > > I am wondering if there are two problems here, rather than just one. So > please could you check a couple of things for me ? > > 1. Does iostream.ex

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #34 from cqwrteur --- (In reply to cqwrteur from comment #33) > (In reply to Nick Clifton from comment #32) > > Hi, > > > > I am wondering if there are two problems here, rather than just one. So > > please could you check a co

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-16 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #33 from cqwrteur --- (In reply to Nick Clifton from comment #32) > Hi, > > I am wondering if there are two problems here, rather than just one. So > please could you check a couple of things for me ? > > 1. Does iostream.ex

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-13 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #30 from cqwrteur --- (In reply to Nick Clifton from comment #24) > Created attachment 14656 [details] > Proposed patch > > Hi, > > Oops - I forgot about section names containing the $ character. > > Please could you try out

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-09 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #28 from cqwrteur --- (In reply to Nick Clifton from comment #24) > Created attachment 14656 [details] > Proposed patch > > Hi, > > Oops - I forgot about section names containing the $ character. > > Please could you try out

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-09 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #29 from cqwrteur --- Created attachment 14666 --> https://sourceware.org/bugzilla/attachment.cgi?id=14666&action=edit This is my build script -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-07 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #27 from cqwrteur --- Created attachment 14659 --> https://sourceware.org/bugzilla/attachment.cgi?id=14659&action=edit iostream -- You are receiving this mail because: You are on the CC list for the bug.

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-07 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #26 from cqwrteur --- (In reply to cqwrteur from comment #25) > (In reply to Nick Clifton from comment #24) > > Created attachment 14656 [details] > > Proposed patch > > > > Hi, > > > > Oops - I forgot about section names conta

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-07 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #25 from cqwrteur --- (In reply to Nick Clifton from comment #24) > Created attachment 14656 [details] > Proposed patch > > Hi, > > Oops - I forgot about section names containing the $ character. > > Please could you try out

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-06 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #22 from cqwrteur --- (In reply to cqwrteur from comment #21) > (In reply to cqwrteur from comment #20) > > (In reply to Nick Clifton from comment #18) > > > Created attachment 14652 [details] > > > Proposed patch > > > > > > Inte

[Bug ld/29973] x86_64-w64-mingw32-g++ ld: helloworld.exe:.rdata_r: section below image base for windows

2023-02-06 Thread euloanty at live dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=29973 --- Comment #23 from cqwrteur --- (In reply to cqwrteur from comment #22) > (In reply to cqwrteur from comment #21) > > (In reply to cqwrteur from comment #20) > > > (In reply to Nick Clifton from comment #18) > > > > Created attachment 14652

  1   2   3   >