https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
YunQiang Su changed:
What|Removed |Added
Resolution|--- |FIXED
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #22 from gagan sidhu (broly) ---
yes it’s fixed sorry.
i foolishly forgot to set the architecture when installing the headers, which
caused the alleged problems.
after i did that, it was completely fixed.
hat tip to the serb on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
YunQiang Su changed:
What|Removed |Added
CC||syq at gcc dot gnu.org
--- Comment #21
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #20 from gagan sidhu (broly) ---
my apologies, i should open a new ticket if this is indeed an error.
but it may be my fault for not specifying the ARCH parameter when installing
the linux headers prior to starting the toolchain.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #19 from gagan sidhu (broly) ---
seems that 13.1.0 still needs some modification, because i was building the
toolchain and now get a static assertion error:
> /bin/sh ../libtool --tag=CXX --mode=compile
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #18 from gagan sidhu (broly) ---
hi,
i wanted to correct an inaccuracy in my previous comment, as i needed to build
a MIPS64 multilib toolchain today and ran into the same problem.
the solution is, as my friend of chinese origin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #17 from gagan sidhu (broly) ---
(In reply to Xi Ruoyao from comment #16)
> (In reply to gagan sidhu (broly) from comment #15)
>
> > and also: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=9f943b2446f2d0
>
> Please don't use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #16 from Xi Ruoyao ---
(In reply to gagan sidhu (broly) from comment #15)
> and also: https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=9f943b2446f2d0
Please don't use this. I've already said why this is not correct in previous
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
gagan sidhu (broly) changed:
What|Removed |Added
CC||broly at mac dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #14 from Xi Ruoyao ---
(In reply to Chris Packham from comment #13)
> (In reply to Xi Ruoyao from comment #12)
> > Please provide info about how libsanitizer end up building with GCC 11.3 and
> > MIPS64 (such a combination is not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #13 from Chris Packham ---
(In reply to Xi Ruoyao from comment #12)
> Please provide info about how libsanitizer end up building with GCC 11.3 and
> MIPS64 (such a combination is not supported and libsanitizer should not be
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Xi Ruoyao changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #12 from Xi Ruoyao
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #11 from Xi Ruoyao ---
> Removing my "fix" resolves the issue for GCC 12 but I suspect something like
> the suggestion from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614#c7
> might resolve the issue properly.
I don't think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Martin Liška changed:
What|Removed |Added
CC||immoloism at googlemail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #8 from Chris Packham ---
In terms of my proposed change which fixes the problem for GCC 11.3.0 it
actually triggers the same assert on GCC 12.1.0.
[ALL ]In file included from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #7 from Hans-Peter Nilsson ---
(In reply to Martin Liška from comment #6)
> The GCC divergence comes from
> https://github.com/gcc-mirror/gcc/commit/
> 9f943b2446f2d0a345bbf9b4be3d3a4316372270
(Why refer to gcc commits through some
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Martin Liška changed:
What|Removed |Added
CC||hp at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #5 from Chris Packham ---
Upstream issue raised https://github.com/llvm/llvm-project/issues/55499 I still
think there's some work on the GCC side required as even without this specific
issue things have diverged.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #4 from Martin Liška ---
Please make the review request to upstream first:
https://reviews.llvm.org/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #3 from Chris Packham ---
It looks like upstream has moved to FIRST_32_SECOND_64(160, 216) somewhere
along the line. According to my reading of the linux source code this is wrong
for both bitnesses now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
--- Comment #2 from Chris Packham ---
Created attachment 52984
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52984=edit
Set struct_kernel_stat_sz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105614
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
23 matches
Mail list logo
