https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111899
Andrew Pinski changed:
What|Removed |Added
Keywords||build
--
You are receiving this mail b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111899
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
--
You are receiving this mail be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111899
--- Comment #2 from Andrew Pinski ---
I noticed it via the build bot:
https://gcc.gnu.org/pipermail/gcc-testresults/2023-October/798851.html
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056
--- Comment #3 from Andrew Pinski ---
Well this is not right:
/var/tmp/portage/sys-devel/gcc-14.0.0_pre20231217/work/build/32/./gcc/xgcc: not
32 should not be there ...
--
You are receiving this mail because:
You are on the CC list for the bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056
--- Comment #4 from Andrew Pinski ---
Looks like multilib support in libgrust is just broken. I suspect it would be
worse on other targets where there are many more multilibs.
--
You are receiving this mail because:
You are on the CC list for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056
Andrew Pinski changed:
What|Removed |Added
Keywords||build
--
You are receiving this mail b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056
--- Comment #6 from Andrew Pinski ---
I just did:
```
mkdir objdir
cd objdir
../configure --enable-languages=rust
make -j24
```
And it work ...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113056
--- Comment #9 from Andrew Pinski ---
I am testing out using an absolute path for configure right now. Seeing if that
changes things ...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113461
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113461
--- Comment #4 from Andrew Pinski ---
Try after r14-8211-g2341df1cb9b3681bfefe29207887b2b3dc271a95 which was just
committed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553
--- Comment #2 from Andrew Pinski ---
Which glibc are you using?
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82346 and maybe
https://sourceware.org/bugzilla/show_bug.cgi?id=22146
--
You are receiving this mail because:
You are on the CC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553
--- Comment #6 from Andrew Pinski ---
(In reply to John Paul Adrian Glaubitz from comment #5)
> (In reply to Rainer Orth from comment #1)
> > The build works for me just fine on sparc-sun-solaris2.11.
> >
> > I've also fired one off on sparc64-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553
Andrew Pinski changed:
What|Removed |Added
See Also||https://sourceware.org/bugz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553
--- Comment #11 from Andrew Pinski ---
(In reply to John Paul Adrian Glaubitz from comment #10)
> (In reply to Andrew Pinski from comment #9)
> > oh look at this a memset issue on sparc glibc:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113553
--- Comment #13 from Andrew Pinski ---
(In reply to Bruno Haible from comment #12)
> For reference: The Gnulib unit tests for posix_spawn* pass on
> sparc-linux-gnu (both in 32-bit mode and in 64-bit mode).
But the issue sounds very intermitten
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629
--- Comment #5 from Andrew Pinski ---
(In reply to Pierre-Emmanuel Patry from comment #2)
> I can see the problem with the message, but I don't think we can remove the
> behavior as we have to match rustc's behavior. The compiler has to ICE when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114629
--- Comment #6 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #5)
> While you are at it, it would be useful to add a link to the rust langauge
> specification (like there is for almost all other languages [I see
> objective-C is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115453
--- Comment #10 from Andrew Pinski ---
(In reply to Arthur Cohen from comment #9)
> Ah, sorry Andrew, I thought the component was referring to the origin of the
> issue. Just wanted to be able to find it in the list of Rust-related issues.
> Sor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115453
Andrew Pinski changed:
What|Removed |Added
Keywords||build
Component|rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116561
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116561
--- Comment #3 from Andrew Pinski ---
Note I think there is still a rust front-end issue. Because if error_mark_node
is making a difference that should not happen since error_mark_node should not
happen as a type unless there is an error and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116561
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
--
You are receiving this mail be
Component: rust
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org,
pierre-emmanuel.patry at embecosm dot com
Target Milestone: ---
I did a `yum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119333
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116561
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2025-03-18
Ever confirmed|0
Priority: P3
Component: rust
Assignee: pinskia at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org,
pierre-emmanuel.patry at embecosm dot com
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119341
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119363
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119342
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119353
Andrew Pinski changed:
What|Removed |Added
CC||doko at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119342
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
Severity: normal
Priority: P3
Component: rust
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org,
pierre-emmanuel.patry at embecosm dot com
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508
--- Comment #2 from Andrew Pinski ---
(In reply to Pierre-Emmanuel Patry from comment #1)
> There is something funny happening here because canonical_paths1.rs should
> not pass, nr2 tests are a list of test with an additional flag. We're using
Priority: P3
Component: rust
Assignee: pinskia at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
CC: dkm at gcc dot gnu.org, gcc-rust at gcc dot gnu.org,
pierre-emmanuel.patry at embecosm dot com
Target Milestone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119341
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119341
--- Comment #1 from Andrew Pinski ---
a few others:
block_add_statements
block
function_set_parameters
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119341
--- Comment #2 from Andrew Pinski ---
function_type_variadic
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119341
--- Comment #3 from Andrew Pinski ---
function_ptr_type uses it already for an example.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119508
--- Comment #4 from Andrew Pinski ---
I wonder if it is showing up due to running the testsuite with -jN
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117869
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119341
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117869
--- Comment #5 from Andrew Pinski ---
And I can confirm I can build rust now.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119342
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108087
Andrew Pinski changed:
What|Removed |Added
Keywords||build
--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108102
Andrew Pinski changed:
What|Removed |Added
Keywords||build
Component|rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108102
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|1 |0
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108102
--- Comment #5 from Andrew Pinski ---
(In reply to Stefan Schulze Frielinghaus from comment #4)
> and the current working directory was most likely /devel/gcc/build/gcc.
> Creating a symlink from $build/stage1-gcc to $build/prev-gcc and then
>
50 matches
Mail list logo