On Feb 13, 2019, at 1:09 AM, Jakub Jelinek wrote:
>
> ok for trunk?
Ok.
On Feb 13, 2019, at 5:37 AM, Jakub Jelinek wrote:
> Here is an updated patch that documents it. Bootstrapped/regtested on
> x86_64-linux and i686-linux, ok for trunk?
Ok.
On Wed, 2019-02-13 at 20:08 +0100, Iain Buclaw wrote:
> On Wed, 13 Feb 2019 at 14:37, Jakub Jelinek wrote:
> >
> > On Wed, Feb 13, 2019 at 10:22:14AM +, Andrew Stubbs wrote:
> > > On 13/02/2019 09:09, Jakub Jelinek wrote:
> > > > To make it work together with doing llvm_binutils only once,
>
On Wed, 13 Feb 2019 at 14:37, Jakub Jelinek wrote:
>
> On Wed, Feb 13, 2019 at 10:22:14AM +, Andrew Stubbs wrote:
> > On 13/02/2019 09:09, Jakub Jelinek wrote:
> > > To make it work together with doing llvm_binutils only once, the global
> > > now
> > > has multiple values
> > > 0 - disallow
On Wed, Feb 13, 2019 at 10:22:14AM +, Andrew Stubbs wrote:
> On 13/02/2019 09:09, Jakub Jelinek wrote:
> > To make it work together with doing llvm_binutils only once, the global now
> > has multiple values
> > 0 - disallow blank lines
> > 1 - allow them for a single test only, reset after
On 13/02/2019 09:09, Jakub Jelinek wrote:
To make it work together with doing llvm_binutils only once, the global now
has multiple values
0 - disallow blank lines
1 - allow them for a single test only, reset after testing it in gcc-dg-prune
2 - allow it for all tests (llvm_binutils)
FWIW, this
Hi!
The following patch fixes various testsuite issues related to
allow_blank_lines.
One issue is that even when llvm_binutils effective target is now cached so
it is checked just once (per runtest invocation), if the first test invoked
emits some diagnostics, that diagnostics in the log file
