public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
@ 2024-06-25 12:52 unlvsur at live dot com
  2024-06-25 12:57 ` [Bug target/115643] " unlvsur at live dot com
                   ` (24 more replies)
  0 siblings, 25 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-25 12:52 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

            Bug ID: 115643
           Summary: aarch64-w64-mingw32 support today breaks
                    x86_64-w64-mingw32 build cannot represent relocation
                    type BFD_RELOC_64
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: unlvsur at live dot com
  Target Milestone: ---

/tmp/ccPA6rty.s: Assembler messages:
/tmp/ccPA6rty.s:758: Error: cannot represent relocation type BFD_RELOC_64
make[4]: *** [Makefile:508: __main.o] Error

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
@ 2024-06-25 12:57 ` unlvsur at live dot com
  2024-06-25 19:36 ` Evgeny.Karpov at microsoft dot com
                   ` (23 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-25 12:57 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #1 from cqwrteur <unlvsur at live dot com> ---
make[4]: Leaving directory
'/home/nagisa/toolchains_build/build/x86_64-w64-mingw32/x86_64-w64-mingw32/artifacts/targetbuild/x86_64-w64-mingw32/gcc/x86_64-w64-mingw32/32/libgcc'
make[3]: *** [Makefile:1221: multi-do] Error 1
make[3]: Leaving directory
'/home/nagisa/toolchains_build/build/x86_64-w64-mingw32/x86_64-w64-mingw32/artifacts/targetbuild/x86_64-w64-mingw32/gcc/x86_64-w64-mingw32/libgcc'
make[2]: *** [Makefile:127: all-multi] Error 2
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
'/home/nagisa/toolchains_build/build/x86_64-w64-mingw32/x86_64-w64-mingw32/artifacts/targetbuild/x86_64-w64-mingw32/gcc/x86_64-w64-mingw32/libgcc'
make[1]: *** [Makefile:15805: all-target-libgcc] Error 2
make[1]: Leaving directory
'/home/nagisa/toolchains_build/build/x86_64-w64-mingw32/x86_64-w64-mingw32/artifacts/targetbuild/x86_64-w64-mingw32/gcc'
make: *** [Makefile:1069: all] Error 2

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
  2024-06-25 12:57 ` [Bug target/115643] " unlvsur at live dot com
@ 2024-06-25 19:36 ` Evgeny.Karpov at microsoft dot com
  2024-06-26 14:15 ` slyfox at gcc dot gnu.org
                   ` (22 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Evgeny.Karpov at microsoft dot com @ 2024-06-25 19:36 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #2 from Evgeny Karpov <Evgeny.Karpov at microsoft dot com> ---
Thanks for reporting the issue.
The patch series has been tested, and regression tests have been executed for
x86_64-w64-mingw32. Could you please provide more details on
which patch triggers the regression? 
It looks more like binutils changes.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
  2024-06-25 12:57 ` [Bug target/115643] " unlvsur at live dot com
  2024-06-25 19:36 ` Evgeny.Karpov at microsoft dot com
@ 2024-06-26 14:15 ` slyfox at gcc dot gnu.org
  2024-06-26 14:22 ` slyfox at gcc dot gnu.org
                   ` (21 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: slyfox at gcc dot gnu.org @ 2024-06-26 14:15 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #3 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
I got a similar failure for `--target=i686-w64-mingw32`. It is probably
slightly dependent on system headers and binutils version. Mine is
binutils-2.42.

I extracted the following self-contained example to crash the build:

// $ cat __main.c.c
extern void *__CTOR_LIST__[];
void __do_global_dtors() {
  if (__CTOR_LIST__[0])
    for (;;)
      ;
}

Crashing:

$ gcc/xgcc -Bgcc/  -fbuilding-libgcc -fno-stack-protector   -c __main.c.c -o
__main.o -O2

i686-w64-mingw32-as: BFD (GNU Binutils) 2.42 assertion fail coff-i386.c:666
/tmp/ccMxDwki.s: Assembler messages:
/tmp/ccMxDwki.s:21: Error: cannot represent relocation type BFD_RELOC_64

I wonder if you can reproduce it with this sample.

Compiler details:

$ gcc/xgcc -Bgcc/ -v
Reading specs from
/tmp/nix-build-i686-w64-mingw32-nolibc-gcc-15.0.0.drv-3/build/./gcc/specs
COLLECT_GCC=/tmp/nix-build-i686-w64-mingw32-nolibc-gcc-15.0.0.drv-3/build/./gcc/xgcc
COLLECT_LTO_WRAPPER=/tmp/nix-build-i686-w64-mingw32-nolibc-gcc-15.0.0.drv-3/build/./gcc/lto-wrapper
Target: i686-w64-mingw32
Configured with: ../source/configure
--prefix=/<<NIX>>/i686-w64-mingw32-nolibc-gcc-15.0.0
--with-gmp-include=/<<NIX>>/gmp-with-cxx-6.3.0-dev/include
--with-gmp-lib=/<<NIX>>/gmp-with-cxx-6.3.0/lib
--with-mpfr-include=/<<NIX>>/mpfr-4.2.1-dev/include
--with-mpfr-lib=/<<NIX>>/mpfr-4.2.1/lib --with-mpc=/<<NIX>>/libmpc-1.3.1
--program-prefix=i686-w64-mingw32- --enable-lto --disable-libstdcxx-pch
--without-included-gettext --with-system-zlib --enable-checking=release
--enable-static --enable-languages=c --disable-multilib --disable-shared
--enable-plugin --with-isl=/<<NIX>>/isl-0.20
--with-as=/<<NIX>>/i686-w64-mingw32-binutils-wrapper-2.42/bin/i686-w64-mingw32-as
--with-ld=/<<NIX>>/i686-w64-mingw32-binutils-wrapper-2.42/bin/i686-w64-mingw32-ld
--disable-libssp --disable-nls --without-headers --disable-threads
--disable-libgomp --disable-libquadmath --disable-shared --disable-libatomic
--disable-decimal-float --disable-libmpx
--with-headers=/<<NIX>>/mingw_w64-headers-11.0.1/include --with-gcc
--with-gnu-as --with-gnu-ld --disable-debug --disable-win32-registry
--enable-hash-synchronization --enable-libssp --disable-nls
--enable-fully-dynamic-string --enable-sjlj-exceptions --with-dwarf2
--disable-bootstrap --build=x86_64-unknown-linux-gnu
--host=x86_64-unknown-linux-gnu --target=i686-w64-mingw32
--with-build-sysroot=/build/source/..
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 15.0.0 99999999 (experimental) (GCC)

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (2 preceding siblings ...)
  2024-06-26 14:15 ` slyfox at gcc dot gnu.org
@ 2024-06-26 14:22 ` slyfox at gcc dot gnu.org
  2024-06-26 20:18 ` slyfox at gcc dot gnu.org
                   ` (20 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: slyfox at gcc dot gnu.org @ 2024-06-26 14:22 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #4 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
`gcc` produces the following assembly:

$ gcc/xgcc -Bgcc  -fbuilding-libgcc -fno-stack-protector   -S __main.c.c -o -
-O2

        .file   "__main.c.c"
        .text
        .p2align 4
        .globl  ___do_global_dtors
        .def    ___do_global_dtors;     .scl    2;      .type   32;     .endef
___do_global_dtors:
        movl    ___CTOR_LIST__, %eax
        testl   %eax, %eax
        je      L1
L3:
        jmp     L3
        .p2align 4,,10
        .p2align 3
L1:
        ret
        .ident  "GCC: (GNU) 15.0.0 99999999 (experimental)"
        .section        .rdata$refptr.__CTOR_LIST__, "dr"
        .globl  refptr.__CTOR_LIST__
        .linkonce       discard
refptr.__CTOR_LIST__:
        .quad   __CTOR_LIST__

`.quad   __CTOR_LIST__` looks wrong for a 32-bit target.

For comparison `gcc-13` produces slightly different result:

$ i686-w64-mingw32-gcc-13.3.0 -fbuilding-libgcc -fno-stack-protector   -S
__main.c.c -o - -O2
        .file   "__main.c.c"
        .text
        .p2align 4
        .globl  ___do_global_dtors
        .def    ___do_global_dtors;     .scl    2;      .type   32;     .endef
___do_global_dtors:
        movl    ___CTOR_LIST__, %eax
        testl   %eax, %eax
        je      L1
L3:
        jmp     L3
        .p2align 4,,10
        .p2align 3
L1:
        ret
        .ident  "GCC: (GNU) 13.3.0"

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (3 preceding siblings ...)
  2024-06-26 14:22 ` slyfox at gcc dot gnu.org
@ 2024-06-26 20:18 ` slyfox at gcc dot gnu.org
  2024-06-26 20:20 ` slyfox at gcc dot gnu.org
                   ` (19 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: slyfox at gcc dot gnu.org @ 2024-06-26 20:18 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #5 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
Bisected down to r15-1602-ged20feebd9ea31 

commit ed20feebd9ea31d58861f61205bd412b0c3febd0
Author: Evgeny Karpov <Evgeny.Karpov@microsoft.com>
Date:   Mon Jun 24 12:46:54 2024 +0000

    Adjust DLL import/export implementation for AArch64

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (4 preceding siblings ...)
  2024-06-26 20:18 ` slyfox at gcc dot gnu.org
@ 2024-06-26 20:20 ` slyfox at gcc dot gnu.org
  2024-06-26 20:38 ` Evgeny.Karpov at microsoft dot com
                   ` (18 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: slyfox at gcc dot gnu.org @ 2024-06-26 20:20 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #6 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #5)
> Bisected down to r15-1602-ged20feebd9ea31 

> +#define PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED \
> +  ix86_cmodel == CM_LARGE_PIC || ix86_cmodel == CM_MEDIUM_PIC

> -  if (ix86_cmodel != CM_LARGE_PIC && ix86_cmodel != CM_MEDIUM_PIC)
> +  if (!PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED)
>      return NULL_RTX;

Missing braces around `PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED`
implementation?

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (5 preceding siblings ...)
  2024-06-26 20:20 ` slyfox at gcc dot gnu.org
@ 2024-06-26 20:38 ` Evgeny.Karpov at microsoft dot com
  2024-06-26 20:57 ` ubizjak at gmail dot com
                   ` (17 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Evgeny.Karpov at microsoft dot com @ 2024-06-26 20:38 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #7 from Evgeny Karpov <Evgeny.Karpov at microsoft dot com> ---
Thanks for pointing that out! The fix will be included in the patch that fixes
the regression.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (6 preceding siblings ...)
  2024-06-26 20:38 ` Evgeny.Karpov at microsoft dot com
@ 2024-06-26 20:57 ` ubizjak at gmail dot com
  2024-06-26 21:09 ` Evgeny.Karpov at microsoft dot com
                   ` (16 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: ubizjak at gmail dot com @ 2024-06-26 20:57 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #8 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Evgeny Karpov from comment #7)
> Thanks for pointing that out! The fix will be included in the patch that
> fixes the regression.

While there, can you perhaps rename:

PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED

to

PE_COFF_LEGITIMIZE_EXTERN_DECL ?

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (7 preceding siblings ...)
  2024-06-26 20:57 ` ubizjak at gmail dot com
@ 2024-06-26 21:09 ` Evgeny.Karpov at microsoft dot com
  2024-06-26 21:52 ` unlvsur at live dot com
                   ` (15 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Evgeny.Karpov at microsoft dot com @ 2024-06-26 21:09 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #9 from Evgeny Karpov <Evgeny.Karpov at microsoft dot com> ---
Sure, it will be included in the patch.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (8 preceding siblings ...)
  2024-06-26 21:09 ` Evgeny.Karpov at microsoft dot com
@ 2024-06-26 21:52 ` unlvsur at live dot com
  2024-06-26 21:52 ` unlvsur at live dot com
                   ` (14 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-26 21:52 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #10 from cqwrteur <unlvsur at live dot com> ---
(In reply to Evgeny Karpov from comment #9)
> Sure, it will be included in the patch.

What's the progression of GCC for aarch64-windows-gnu? How long would it be
done? I want to buy a surface pro 11 to use it.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (9 preceding siblings ...)
  2024-06-26 21:52 ` unlvsur at live dot com
@ 2024-06-26 21:52 ` unlvsur at live dot com
  2024-06-27  2:08 ` [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31 sjames at gcc dot gnu.org
                   ` (13 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-26 21:52 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #11 from cqwrteur <unlvsur at live dot com> ---
(In reply to Evgeny Karpov from comment #9)
> Sure, it will be included in the patch.

BTW, any plans for riscv and loongarch support for Windows GCC?

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (10 preceding siblings ...)
  2024-06-26 21:52 ` unlvsur at live dot com
@ 2024-06-27  2:08 ` sjames at gcc dot gnu.org
  2024-06-27  3:56 ` pinskia at gcc dot gnu.org
                   ` (12 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: sjames at gcc dot gnu.org @ 2024-06-27  2:08 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|aarch64-w64-mingw32 support |[15 regression]
                   |today breaks                |aarch64-w64-mingw32 support
                   |x86_64-w64-mingw32 build    |today breaks
                   |cannot represent relocation |x86_64-w64-mingw32 build
                   |type BFD_RELOC_64           |cannot represent relocation
                   |                            |type BFD_RELOC_64 since
                   |                            |r15-1602-ged20feebd9ea31
           Assignee|unassigned at gcc dot gnu.org      |Evgeny.Karpov at microsoft dot com
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2024-06-27

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (11 preceding siblings ...)
  2024-06-27  2:08 ` [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31 sjames at gcc dot gnu.org
@ 2024-06-27  3:56 ` pinskia at gcc dot gnu.org
  2024-06-27  7:25 ` Evgeny.Karpov at microsoft dot com
                   ` (11 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: pinskia at gcc dot gnu.org @ 2024-06-27  3:56 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |15.0
           Keywords|                            |link-failure

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (12 preceding siblings ...)
  2024-06-27  3:56 ` pinskia at gcc dot gnu.org
@ 2024-06-27  7:25 ` Evgeny.Karpov at microsoft dot com
  2024-06-28  8:39 ` Evgeny.Karpov at microsoft dot com
                   ` (10 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Evgeny.Karpov at microsoft dot com @ 2024-06-27  7:25 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #12 from Evgeny Karpov <Evgeny.Karpov at microsoft dot com> ---
Thank you for reporting the issues and discussing the root causes. 
It helped in preparing the patch.

The patch is under review.
https://gcc.gnu.org/pipermail/gcc-patches/2024-June/655807.html

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (13 preceding siblings ...)
  2024-06-27  7:25 ` Evgeny.Karpov at microsoft dot com
@ 2024-06-28  8:39 ` Evgeny.Karpov at microsoft dot com
  2024-06-28  8:40 ` unlvsur at live dot com
                   ` (9 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: Evgeny.Karpov at microsoft dot com @ 2024-06-28  8:39 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #13 from Evgeny Karpov <Evgeny.Karpov at microsoft dot com> ---
Could you please confirm that the patch resolves the issue?

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (14 preceding siblings ...)
  2024-06-28  8:39 ` Evgeny.Karpov at microsoft dot com
@ 2024-06-28  8:40 ` unlvsur at live dot com
  2024-06-28  8:40 ` unlvsur at live dot com
                   ` (8 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-28  8:40 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #14 from cqwrteur <unlvsur at live dot com> ---
(In reply to Evgeny Karpov from comment #13)
> Could you please confirm that the patch resolves the issue?

why should I? As a microsoft sholder i would say fuck you for using gmail and
google bs

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (15 preceding siblings ...)
  2024-06-28  8:40 ` unlvsur at live dot com
@ 2024-06-28  8:40 ` unlvsur at live dot com
  2024-06-28  8:45 ` unlvsur at live dot com
                   ` (7 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-28  8:40 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #15 from cqwrteur <unlvsur at live dot com> ---
(In reply to Evgeny Karpov from comment #13)
> Could you please confirm that the patch resolves the issue?

People like you need to be fired

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (16 preceding siblings ...)
  2024-06-28  8:40 ` unlvsur at live dot com
@ 2024-06-28  8:45 ` unlvsur at live dot com
  2024-06-28  8:49 ` unlvsur at live dot com
                   ` (6 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-28  8:45 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #16 from cqwrteur <unlvsur at live dot com> ---
This is insane. I am a Microsoft shareholder so technically I am your boss. Why
would you ask your boss to waste time for doing your job?

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

________________________________
From: Evgeny.Karpov at microsoft dot com <gcc-bugzilla@gcc.gnu.org>
Sent: Friday, June 28, 2024 4:39:24 AM
To: unlvsur@live.com <unlvsur@live.com>
Subject: [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today
breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #13 from Evgeny Karpov <Evgeny.Karpov at microsoft dot com> ---
Could you please confirm that the patch resolves the issue?

--
You are receiving this mail because:
You reported the bug.
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (17 preceding siblings ...)
  2024-06-28  8:45 ` unlvsur at live dot com
@ 2024-06-28  8:49 ` unlvsur at live dot com
  2024-06-28  9:07 ` slyfox at gcc dot gnu.org
                   ` (5 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-28  8:49 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #17 from cqwrteur <unlvsur at live dot com> ---
https://github.com/trcrsired/toolchainbuildscripts/blob/main/gccbuild/x86_64-w64-mingw32/x86_64-w64-mingw32.sh


Here is the automatic script. Go and test yourself

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (18 preceding siblings ...)
  2024-06-28  8:49 ` unlvsur at live dot com
@ 2024-06-28  9:07 ` slyfox at gcc dot gnu.org
  2024-06-28  9:13 ` unlvsur at live dot com
                   ` (4 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: slyfox at gcc dot gnu.org @ 2024-06-28  9:07 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #18 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Evgeny Karpov from comment #13)
> Could you please confirm that the patch resolves the issue?

The change fixes --target=i686-w64-mingw32 for me. Thank you!

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (19 preceding siblings ...)
  2024-06-28  9:07 ` slyfox at gcc dot gnu.org
@ 2024-06-28  9:13 ` unlvsur at live dot com
  2024-06-28  9:19 ` redi at gcc dot gnu.org
                   ` (3 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-28  9:13 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #19 from cqwrteur <unlvsur at live dot com> ---
Then just merge it into the main repo if it works. I have no time for testing
because my machine is super slow and I have no idea what’s going on.

BTW, it is still insane Microsoft employee would ask Microsoft shareholder to
test for him.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

________________________________
From: slyfox at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Friday, June 28, 2024 5:07:40 AM
To: unlvsur@live.com <unlvsur@live.com>
Subject: [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today
breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #18 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Evgeny Karpov from comment #13)
> Could you please confirm that the patch resolves the issue?

The change fixes --target=i686-w64-mingw32 for me. Thank you!

--
You are receiving this mail because:
You reported the bug.
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (20 preceding siblings ...)
  2024-06-28  9:13 ` unlvsur at live dot com
@ 2024-06-28  9:19 ` redi at gcc dot gnu.org
  2024-06-28  9:34 ` unlvsur at live dot com
                   ` (2 subsequent siblings)
  24 siblings, 0 replies; 26+ messages in thread
From: redi at gcc dot gnu.org @ 2024-06-28  9:19 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #20 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Your attitude and behaviour is not acceptable, as you've been told many times
before.

You will be banned if you continue.

https://gcc.gnu.org/conduct.html

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (21 preceding siblings ...)
  2024-06-28  9:19 ` redi at gcc dot gnu.org
@ 2024-06-28  9:34 ` unlvsur at live dot com
  2024-06-28 12:47 ` cvs-commit at gcc dot gnu.org
  2024-06-28 12:51 ` clyon at gcc dot gnu.org
  24 siblings, 0 replies; 26+ messages in thread
From: unlvsur at live dot com @ 2024-06-28  9:34 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #21 from cqwrteur <unlvsur at live dot com> ---
First, the bug is not caused by me and I am just reporting the issue here. Why
should I waste my time to test for him?

Second, I am tired of building compilers again and again just to fix a
regression every day. My machine is super slow with no SSD.

BTW do I even make a decision on whether a patch would get merged into GCC? Did
you merge my patch on fixing libstdc++’s abi break? Oh it does not follow your
“code standard” plus you hate me for that freestanding thing and I get it. Ok,
then fix it yourself.

Sorry, I am not going to do either of them. I am not going to test it and I am
not going to fix the ABI bug. It is better you don’t fix the ABI regression and
let the GNU/Linux die.

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows

________________________________
From: redi at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
Sent: Friday, June 28, 2024 5:19:03 AM
To: unlvsur@live.com <unlvsur@live.com>
Subject: [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today
breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
since r15-1602-ged20feebd9ea31

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #20 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Your attitude and behaviour is not acceptable, as you've been told many times
before.

You will be banned if you continue.

https://gcc.gnu.org/conduct.html

--
You are receiving this mail because:
You are on the CC list for the bug.
You reported the bug.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (22 preceding siblings ...)
  2024-06-28  9:34 ` unlvsur at live dot com
@ 2024-06-28 12:47 ` cvs-commit at gcc dot gnu.org
  2024-06-28 12:51 ` clyon at gcc dot gnu.org
  24 siblings, 0 replies; 26+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2024-06-28 12:47 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

--- Comment #22 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>:

https://gcc.gnu.org/g:c4b7b62bfa10816c1e08f0f9597d857f11379688

commit r15-1708-gc4b7b62bfa10816c1e08f0f9597d857f11379688
Author: Evgeny Karpov <Evgeny.Karpov@microsoft.com>
Date:   Fri Jun 28 12:37:12 2024 +0000

    i386: Fix regression after refactoring legitimize_pe_coff_symbol,
ix86_GOT_alias_set and PE_COFF_LEGITIMIZE_EXTERN_DECL [PR115635]

    This patch fixes 3 bugs reported after merging the "Add DLL
    import/export implementation to AArch64" series.
    https://gcc.gnu.org/pipermail/gcc-patches/2024-June/653955.html The
    series refactors the i386 codebase to reuse it in AArch64, which
    triggers some bugs.

    Bug 115661 - [15 Regression] wrong code at -O{2,3} on x86_64-linux-gnu
    since r15-1599-g63512c72df09b4
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115661

    Bug 115635 - [15 regression] Bootstrap fails with failed self-test
    with the rust fe (diagnostic-path.cc:1153: test_empty_path: FAIL:
    ASSERT_FALSE ((path.interprocedural_p ()))) since
    r15-1599-g63512c72df09b4
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115635

    Issue 1. In some code, i386 has been relying on the
    legitimize_pe_coff_symbol call on all platforms and should return
    NULL_RTX if it is not supported.

    Fix: NULL_RTX handling has been added when the target does not support
    PECOFF.

    Issue 2. ix86_GOT_alias_set is used on all platforms and cannot be
    extracted to mingw.

    Fix: ix86_GOT_alias_set has been returned as it was and is used on all
    platforms for i386.

    Bug 115643 - [15 regression] aarch64-w64-mingw32 support today breaks
    x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64
    since r15-1602-ged20feebd9ea31
    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

    Issue 3. PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED has been added and
    used with a negative operator for a complex expression without braces.

    Fix: Braces has been added, and
    PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED has been renamed to
    PE_COFF_LEGITIMIZE_EXTERN_DECL.

    2024-06-28  Evgeny Karpov <Evgeny.Karpov@microsoft.com>

            gcc/ChangeLog:
            PR bootstrap/115635
            PR target/115643
            PR target/115661
            * config/aarch64/cygming.h
            (PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED): Rename to
            PE_COFF_LEGITIMIZE_EXTERN_DECL.
            (PE_COFF_LEGITIMIZE_EXTERN_DECL): Likewise.
            * config/i386/cygming.h (GOT_ALIAS_SET): Remove the diffinition to
            reuse it from i386.h.
            (PE_COFF_EXTERN_DECL_SHOULD_BE_LEGITIMIZED): Rename to
            PE_COFF_LEGITIMIZE_EXTERN_DECL.
            (PE_COFF_LEGITIMIZE_EXTERN_DECL): Likewise.
            * config/i386/i386-expand.cc (ix86_expand_move): Return
            ix86_GOT_alias_set.
            * config/i386/i386-expand.h (ix86_GOT_alias_set): Likewise.
            * config/i386/i386.cc (ix86_GOT_alias_set): Likewise.
            * config/i386/i386.h (GOT_ALIAS_SET): Likewise.
            * config/mingw/winnt-dll.cc (get_dllimport_decl): Use
            GOT_ALIAS_SET.
            (legitimize_pe_coff_symbol): Rename to
            PE_COFF_LEGITIMIZE_EXTERN_DECL.
            * config/mingw/winnt-dll.h (ix86_GOT_alias_set): Declare
            ix86_GOT_alias_set.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31
  2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
                   ` (23 preceding siblings ...)
  2024-06-28 12:47 ` cvs-commit at gcc dot gnu.org
@ 2024-06-28 12:51 ` clyon at gcc dot gnu.org
  24 siblings, 0 replies; 26+ messages in thread
From: clyon at gcc dot gnu.org @ 2024-06-28 12:51 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115643

Christophe Lyon <clyon at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |clyon at gcc dot gnu.org
             Status|ASSIGNED                    |RESOLVED

--- Comment #23 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Fixed

^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, other threads:[~2024-06-28 12:51 UTC | newest]

Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-25 12:52 [Bug target/115643] New: aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 unlvsur at live dot com
2024-06-25 12:57 ` [Bug target/115643] " unlvsur at live dot com
2024-06-25 19:36 ` Evgeny.Karpov at microsoft dot com
2024-06-26 14:15 ` slyfox at gcc dot gnu.org
2024-06-26 14:22 ` slyfox at gcc dot gnu.org
2024-06-26 20:18 ` slyfox at gcc dot gnu.org
2024-06-26 20:20 ` slyfox at gcc dot gnu.org
2024-06-26 20:38 ` Evgeny.Karpov at microsoft dot com
2024-06-26 20:57 ` ubizjak at gmail dot com
2024-06-26 21:09 ` Evgeny.Karpov at microsoft dot com
2024-06-26 21:52 ` unlvsur at live dot com
2024-06-26 21:52 ` unlvsur at live dot com
2024-06-27  2:08 ` [Bug target/115643] [15 regression] aarch64-w64-mingw32 support today breaks x86_64-w64-mingw32 build cannot represent relocation type BFD_RELOC_64 since r15-1602-ged20feebd9ea31 sjames at gcc dot gnu.org
2024-06-27  3:56 ` pinskia at gcc dot gnu.org
2024-06-27  7:25 ` Evgeny.Karpov at microsoft dot com
2024-06-28  8:39 ` Evgeny.Karpov at microsoft dot com
2024-06-28  8:40 ` unlvsur at live dot com
2024-06-28  8:40 ` unlvsur at live dot com
2024-06-28  8:45 ` unlvsur at live dot com
2024-06-28  8:49 ` unlvsur at live dot com
2024-06-28  9:07 ` slyfox at gcc dot gnu.org
2024-06-28  9:13 ` unlvsur at live dot com
2024-06-28  9:19 ` redi at gcc dot gnu.org
2024-06-28  9:34 ` unlvsur at live dot com
2024-06-28 12:47 ` cvs-commit at gcc dot gnu.org
2024-06-28 12:51 ` clyon at gcc dot gnu.org

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).