On Sun, 2022-06-26 at 14:06 +0100, Iain Sandoe wrote:
> Hi Dave, folks,
>
> It seems to me that it is plausible that one could use the JIT in a
> heterogenous system, e.g. an x86_64-linux-host with some kind of co-
> processor which is supported as a GCC target (and therefore can be
> loaded with
Hi Dave,
Note: this does cause a build break for cross compilers with
—enable-languages=all (if the linkers for host and target have different
command line options used in the build)
(it is not a serious break, one can exclude jit by manually listing all the
other languages)
- nevertheless,
To aid in debugging and instrumentation (we would like to look at a stopped
program and unwind while recording all argument values), I would like to
either store a copy of all register arguments on the caller's stack or
record them in the callee's stack on function entry.
Both options are straight
Thanks for suggestion, definitely doable, more verbose vs the scanf, but will
do the trick. I will use it as my fallback, if no path with my current
approach. Yair. Sent from my iPad
> On Jul 6, 2022, at 10:17 AM, David Brown wrote:
>
> I haven't worked through all the details, but I wonder if
On 05/07/2022 09:19, Yair Lenga via Gcc wrote:
Hi,
Wanted to get some feedback on an idea that I have - trying to address the
age long issue with type check on VA list function - like 'scanf' and
friends. In my specific case, I'm trying to build code that will parse a
list of values from SELECT
