[Bug rust/113499] crab1 fails to link when configuring with --disable-plugin

[cohenarthur at gcc dot gnu.org]

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

--- Comment #6 from Arthur Cohen  ---
(In reply to Richard Biener from comment #5)
> (In reply to Thomas Schwinge from comment #4)
> > If I understood Arthur correctly, GCC/Rust is going to effectively require
> > 'dlopen' (and therefore '--enable-plugin'?), so that means, if the latter's
> > not available we have to auto-disable Rust language front end if enabled
> > '--enable-languages=all' vs. raise a 'configure'-time error if enabled via
> > explicit '--enable-languages=rust'?
> 
> Not sure - --enable-plugin is not about dlopen, it's about exporting all
> GCCs internal symbols for use by a dlopened shared module.  Is the
> macro processing requiring this or is it rather self-contained?
> 
> Being able to dlopen() is something different.

No, it does not require this and is rather self contained. Macro expansion
needs to be able to dlopen() compiled Rust libraries, which contain a specific
type of function our frontend calls as a macro. So we always need to dlopen().

Is there anything similar in other frontends? If so, how does it work on such
platforms which do not support dlopen()?

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

[Bug bootstrap/115453] [15 regression] Noise from new dlopen, pthread configure checks since r15-1177-g75299e4fe50aa8

[cohenarthur at gcc dot gnu.org]

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

--- Comment #9 from Arthur Cohen  ---
(In reply to Andrew Pinski from comment #8)
> Toplevel makefile is consider bootstrap component rather than rust ...

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.
Sorry!

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

[Bug rust/115453] [15 regression] Noise from new dlopen, pthread configure checks since r15-1177-g75299e4fe50aa8

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 CC||dkm at gcc dot gnu.org,
   ||gcc-rust at gcc dot gnu.org
  Component|bootstrap   |rust

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

[Bug rust/116192] [15 regression] 32-bit rust build fails

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 CC||cohenarthur at gcc dot gnu.org
   Assignee|unassigned at gcc dot gnu.org  |cohenarthur at gcc dot 
gnu.org

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

[Bug rust/116192] [15 regression] 32-bit rust build fails

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 Status|UNCONFIRMED |ASSIGNED
   Last reconfirmed||2024-08-02
 Ever confirmed|0   |1

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

[Bug rust/116192] [15 regression] 32-bit rust build fails

[cohenarthur at gcc dot gnu.org]

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

--- Comment #2 from Arthur Cohen  ---
Hi Rainer,

Thank you for the report. We've fixed this in our development repository and
will upstream the commits soon. I am looking at adding a 32-bit CI build so
that this does not happen again.

Best,

Arthur

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

[Bug rust/116192] [15 regression] 32-bit rust build fails

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #4 from Arthur Cohen  ---
Ah right, sorry about that. I'll think about it for next time. One of our GSoC
students has also contributed a 32bit CI to our project, so hopefully this sort
of thing will no longer happen.

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

[Bug rust/119353] [15 regression] Rust fails to build (build failure: error[E0554]: `#![feature]` may not be used on the stable release channel)

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

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

[Bug rust/119353] [15 regression] Rust fails to build (build failure: error[E0554]: `#![feature]` may not be used on the stable release channel)

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 CC||cohenarthur at gcc dot gnu.org

--- Comment #5 from Arthur Cohen  ---
One of our milestones for 15.1 is to get all Rust code compilable with a Rust
1.49 compiler, so any of these versions will work fine once we are done
upstreaming for the next GCC release. As Pierre-Emmanuel said this is already
done in our development repository, so this PR will be fixed soon.

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

[Bug rust/119353] [15 regression] Rust fails to build (build failure: error[E0554]: `#![feature]` may not be used on the stable release channel)

[cohenarthur at gcc dot gnu.org]

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

--- Comment #9 from Arthur Cohen  ---
This should now be fixed by our latest patch upload. If anyone would like to
try again and report back please do, and I'll close this out

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

[Bug rust/119641] narrowing Warning during bootstrap in Rust::BIR::PlaceDB::lookup_or_add_variable

[cohenarthur at gcc dot gnu.org]

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

--- Comment #6 from Arthur Cohen  ---
(In reply to Thomas Schwinge from comment #3)
> (I haven't checked, but) supposedly fixed in trunk via commit
> r16-237-gbeced835afa3908aa94550d2ca5ee3879a620adb "gccrs: Fix narrowing
> conversion warnings".
> 
> Owen, for next time, to auto-annotate GCC Bugzilla, the correct syntax to
> use in Git log would've been to put "PR rust/119641" into the ChangeLog
> snippet, see .
> 
> Given this has been filed with "Version: 15.0", should this be cherry-picked
> into releases/gcc-15 branch as well?

Yes, I think it'd be good to get it in 15.2 as well. We can submit the patches
for a review once we fix the last narrowing conversion I think.

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

[Bug rust/119641] narrowing Warning during bootstrap in Rust::BIR::PlaceDB::lookup_or_add_variable

[cohenarthur at gcc dot gnu.org]

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

Arthur Cohen  changed:

   What|Removed |Added

 CC||cohenarthur at gcc dot gnu.org

--- Comment #2 from Arthur Cohen  ---
This won't be upstreamed for a bit as we are waiting until the release to
upstream again, so that we don't disturb trunk too much. But yeah we do have a
fix in our dev repo and it's under review :)

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

[Bug rust/108087] -Wodr warnings in rust/rust-lang.cc (lang_type)

[cohenarthur at gcc dot gnu.org via Gcc-rust]

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

Arthur Cohen  changed:

   What|Removed |Added

 CC||cohenarthur at gcc dot gnu.org
   See Also||https://github.com/Rust-GCC
   ||/gccrs/issues/1702

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

[Bug rust/108087] -Wodr warnings in rust/rust-lang.cc (lang_type)

[cohenarthur at gcc dot gnu.org via Gcc-rust]

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

Arthur Cohen  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

[Bug rust/108631] gcc/rust/backend/rust-constexpr.cc:2099:33: error: too few arguments to function ‘tree_node* Rust::Compile::unshare_constructor(tree, const char*, int, const char*)’ with --enable-ga

[cohenarthur at gcc dot gnu.org via Gcc-rust]

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

Arthur Cohen  changed:

   What|Removed |Added

 Ever confirmed|0   |1
   Last reconfirmed||2023-02-09
 Status|UNCONFIRMED |NEW

--- Comment #2 from Arthur Cohen  ---
Patch looks good to me Martin, thank you. Will you push it directly?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust

[Bug rust/108631] gcc/rust/backend/rust-constexpr.cc:2099:33: error: too few arguments to function ‘tree_node* Rust::Compile::unshare_constructor(tree, const char*, int, const char*)’ with --enable-ga

[cohenarthur at gcc dot gnu.org via Gcc-rust]

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

Arthur Cohen  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|unassigned at gcc dot gnu.org  |cohenarthur at gcc dot 
gnu.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
Gcc-rust mailing list
Gcc-rust@gcc.gnu.org
https://gcc.gnu.org/mailman/listinfo/gcc-rust