On Wed, May 27, 2020 at 10:16 AM Alexandre Oliva <ol...@adacore.com> wrote: > > Hello, David, > > On May 26, 2020, David Edelsohn <dje....@gmail.com> wrote: > > > Complaints about -dA, -dD, -dumpbase, etc. > > This was the main symptom of the problem fixed in the follow-up commit > r11-635-g6232d02b4fce4c67d39815aa8fb956e4b10a4e1b > > Could you please confirm that you did NOT have this commit in your > failing build, and that the patch above fixes the problem for you as it > did for others?
Hi, Alexandre Thanks for diligently working on this issue. I did not have the fix mentioned above in the original test. I am performing a new bootstrap with the patch. Hopefully it will address some or all of the issues. DejaGNU and the GCC testsuite is what it is. It is fragile. One of the strengths of GCC is the wide variety of targets supported, not only GNU/Linux, but other Unixes, Windows, embedded. Testsuite infrastructure changes such as these need testing on a wide variety of targets to find system dependencies. Thanks, David
