https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117010
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2025-03-25 00:00:00 |2025-4-16
Resolution|--- |DUPLICATE
Status|ASSIGNED |RESOLVED
--- Comment #10 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to myself from comment #8)
> [...] Offloading code generation uses the LTO machinery, including
> the 'lto1' front end, and thus has 'gcc/common.opt:in_lto_p' set to 'true':
> [...]
> [...] What this means semantically: whether
> 'in_lto_p' should vs. shouldn't actually be set for offloading compilation,
> I/we have to spend more thought on, whether all these
> transformations/optimizations guarded by 'in_lto_p' are generally applicable
> to offloading compilation or not?
-> PR119833 "Clarify which semantics offloading compilation does (not) inherit
from using the LTO infrastructure".
(In reply to myself from comment #9)
> (..., but I've found another "solution" to the original problem; to be
> detailed later.)
The original problem now is exactly PR97106.
*** This bug has been marked as a duplicate of bug 97106 ***
