GNU bug report logs - #76180
[feature/igc] Remaining known tracing issues

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> protonmail.com>
Cc: eggert <at> cs.ucla.edu, 76180 <at> debbugs.gnu.org, mattiase <at> acm.org, gerd.moellmann <at> gmail.com, stefankangas <at> gmail.com, acorallo <at> gnu.org
Subject: bug#76180: [feature/igc] Remaining known tracing issues
Date: Fri, 14 Feb 2025 14:38:15 +0200

> Date: Fri, 14 Feb 2025 12:31:15 +0000
> From: Pip Cet <pipcet <at> protonmail.com>
> Cc: acorallo <at> gnu.org, stefankangas <at> gmail.com, 76180 <at> debbugs.gnu.org, gerd.moellmann <at> gmail.com, mattiase <at> acm.org, eggert <at> cs.ucla.edu
> 
> "Eli Zaretskii" <eliz <at> gnu.org> writes:
> 
> > Alternatively, maybe the nativecomp code could be modified not to use
> > RBP?
> 
> I'm not sure what you mean: the code is generated by libgccjit.

Oh, I didn't realize that.  If we really have no control over this,
then maybe a bug report against libgccjit is in order?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.