It is desirable to add in a patch message the tests which are failing, at least an overview (something like: execute.exp: 123 failings). It is also important to specify how to reproduce the issue (which configuration, if you use main gcc's branch or not). Providing some examples, like you did in the last email, helps me, and any other person, to understand the nature of your patch. I'll come back to you as soon as possible, Claudiu
On Sat, Jul 25, 2026 at 12:01 AM Derhaeg, Michiel <[email protected]> wrote: > > Hi Claudiu, > > > Can you make a test showing the current issue? > Are you sure? If you insist I'd be happy to, but there are already plenty of > tests that expose this issue: > > For example: > gcc.c-torture/execute/pr23135.c > gcc.c-torture/execute/pr53645.c > gcc.c-torture/execute/scal-to-vec1.c > gcc.c-torture/execute/scal-to-vec2.c > gcc.c-torture/execute/simd-1.c > gcc.dg/pr88598-4. > > Kind regards, > Michiel Derhaeg
