Re: [PATCH 24/25] Ignore LLVM's blank lines.

2020-03-24 Thread Thomas Schwinge
Hi! On 2020-03-23T16:29:40+0100, I wrote: > On 2018-09-14T10:18:12-0600, Jeff Law wrote: >> On 9/5/18 5:52 AM, a...@codesourcery.com wrote: >>> >>> The GCN toolchain must use the LLVM assembler and linker because there's no >>> binutils port. The LLVM tools do not have the same diagnostic style

Re: [PATCH 24/25] Ignore LLVM's blank lines.

2020-03-23 Thread Thomas Schwinge
Hi! Now that I'm looking into enabling AMD GCN offloading in my builds, I have a few concerns here. ;-) On 2018-09-14T10:18:12-0600, Jeff Law wrote: > On 9/5/18 5:52 AM, a...@codesourcery.com wrote: >> >> The GCN toolchain must use the LLVM assembler and linker because there's no >> binutils po

Re: [PATCH 24/25] Ignore LLVM's blank lines.

2018-09-14 Thread Jeff Law
On 9/5/18 5:52 AM, a...@codesourcery.com wrote: > > The GCN toolchain must use the LLVM assembler and linker because there's no > binutils port. The LLVM tools do not have the same diagnostic style as > binutils, so the "blank line(s) in output" tests are inappropriate (and very > noisy). > > Th

[PATCH 24/25] Ignore LLVM's blank lines.

2018-09-05 Thread ams
The GCN toolchain must use the LLVM assembler and linker because there's no binutils port. The LLVM tools do not have the same diagnostic style as binutils, so the "blank line(s) in output" tests are inappropriate (and very noisy). The LLVM tools also have different command line options, so it's