public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iains.gcc@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, FX Coudert <fxcoudert@gmail.com>
Subject: Re: gfortran.dg/dg.exp debug messages pollute test output
Date: Mon, 13 Nov 2023 06:19:29 -1000	[thread overview]
Message-ID: <CF837686-AFA9-4920-84AF-6C0CC314CC67@gmail.com> (raw)
In-Reply-To: <yddedgt7jx4.fsf@CeBiTec.Uni-Bielefeld.DE>

Hi Rainer,

> On 13 Nov 2023, at 05:27, Rainer Orth <ro@cebitec.uni-bielefeld.de> wrote:
> 
> I happened to notice that make check output is cluttered with the likes
> of
> 
> dg set al  -B/var/gcc/regression/master/11.4-gcc/build/i386-pc-solaris2.11/./libatomic/  -B/var/gcc/regression/master/11.4-gcc/build/i386-pc-solaris2.11/./libatomic/.libs ml /var/gcc/regression/master/11.4-gcc/build/i386-pc-solaris2.11/.
> revised FFLAGS -pedantic-errors -B/var/gcc/regression/master/11.4-gcc/build/i386-pc-solaris2.11/./libatomic/ -B/var/gcc/regression/master/11.4-gcc/build/i386-pc-solaris2.11/./libatomic/.libs
> 
> (quite a number of instances).  Those messages are from
> gfortran.dg/dg.exp, introduced by your patch
> 
> commit a0673ec5f9236dca6ada23f28343c591ccd575e4
> Author: Iain Sandoe <iain@sandoe.co.uk>
> Date:   Fri Apr 16 20:01:40 2021 +0100
> 
>    Testsuite: allow non-installed testing on darwin
> 
> I couldn't find any submission for that patch, unfortunately.  

FX submitted the patch series, I can find the reference if you need it.

> Besides,
> it's unclear if those messages can just be removed (they are pretty
> cryptic as is) or at least changed to use verbose instead of puts.
> Please fix.

will do.
thanks
Iain

> 
> 	Rainer
> 
> -- 
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University


  reply	other threads:[~2023-11-13 16:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 16:58 Darwin: Replace environment runpath with embedded [PR88590] FX Coudert
2023-08-18 20:17 ` Joseph Myers
2023-08-18 22:31   ` Iain Sandoe
2023-08-18 22:59     ` Joseph Myers
2023-08-18 23:05       ` Iain Sandoe
2023-08-25  7:50   ` FX Coudert
2023-08-25 16:28     ` Joseph Myers
2023-08-29 16:06       ` FX Coudert
2023-08-29 19:55         ` Joseph Myers
2023-08-29 20:17           ` FX Coudert
2023-09-12 17:52             ` FX Coudert
2023-09-20 13:52               ` FX Coudert
2023-10-08 13:07                 ` Nathanael Nerode
2023-10-08 22:14                   ` Iain Sandoe
2023-10-21 18:05                     ` Jeff Law
2023-10-21 18:26                       ` Iain Sandoe
2023-10-21  5:27             ` Alexandre Oliva
2023-10-22 21:18               ` FX Coudert
2023-11-30 19:43                 ` Ian Lance Taylor
2023-11-30 19:56                   ` Iain Sandoe
2023-11-30 19:58                     ` Ian Lance Taylor
2023-11-30 21:25                       ` Ian Lance Taylor
2023-10-30 16:17 ` Martin Jambor
     [not found] ` <653fd72a.050a0220.a6a20.de86SMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-30 16:19   ` Iain Sandoe
2023-10-30 16:31   ` FX Coudert
2023-10-30 19:08     ` Iain Sandoe
2023-11-15 20:11       ` Thomas Schwinge
2023-11-15 20:34         ` FX Coudert
2023-11-17 11:56           ` FX Coudert
2023-11-17 12:13             ` Thomas Schwinge
2023-11-17 14:20               ` FX Coudert
2023-11-22 10:52                 ` Iain Sandoe
2023-11-22 10:55                   ` FX Coudert
2023-11-13 15:27 ` gfortran.dg/dg.exp debug messages pollute test output Rainer Orth
2023-11-13 16:19   ` Iain Sandoe [this message]
2023-11-15 10:29     ` FX Coudert
2023-11-15 12:04       ` Rainer Orth
2023-11-17 12:36       ` Thomas Schwinge
2023-11-18  9:03         ` FX Coudert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CF837686-AFA9-4920-84AF-6C0CC314CC67@gmail.com \
    --to=iains.gcc@gmail.com \
    --cc=fxcoudert@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@cebitec.uni-bielefeld.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).