On Thu, 2022-12-01 at 10:25 -0500, David Malcolm wrote: > On Thu, 2022-12-01 at 10:01 -0500, Antoni Boucher wrote: > > Thanks, David. > > Since we're not in phase 1 anymore, do we need an approval before I > > merge like last year or can I merge immediately? > > I think it counts as a bug fix and thus you can go ahead and merge > (assuming you've done the usual testing). > > > I also have many other patches (all in jit) that I need to prepare > > and > > post to this mailing list. > > What do you think? > > Given that you're one of the main users of libgccjit I think there's > a > case for stretching the deadlines a bit here. > > Do you have a repo I can look at?
Yes! The commits are in my fork: https://github.com/antoyo/gcc The only big one is the one adding support for target-dependent builtins: https://github.com/antoyo/gcc/commit/6d4313d4c02dd878f43917c978f299f5119330f0 Regarding this one, there's the issue that since we record the builtins on the first context run, we only have access to the builtins from the second run. Do you have any idea how to fix this? Or do you consider this is acceptable? I also have a WIP branch which adds support for try/catch: https://github.com/antoyo/gcc/commit/6219339fcacb079431596a0bc6cf8d430a1bd5a1 I'm not sure if this one is going to be ready soon or not. Thanks. > > Dave > > > > > > On Thu, 2022-12-01 at 09:28 -0500, David Malcolm wrote: > > > On Sun, 2022-11-20 at 14:03 -0500, Antoni Boucher via Jit wrote: > > > > Hi. > > > > This fixes bug 107770. > > > > Thanks for the review. > > > > > > Thanks, the patch looks good to me. > > > > > > Dave > > > > > >
