public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-10455] LTO: Prune some warnings in the testsuite
Date: Fri,  6 Jan 2023 09:17:15 +0000 (GMT)	[thread overview]
Message-ID: <20230106091715.BA6A33858D33@sourceware.org> (raw)

https://gcc.gnu.org/g:65b768fdb1ad302a6537119305317f413bfcbe0e

commit r11-10455-g65b768fdb1ad302a6537119305317f413bfcbe0e
Author: Francois-Xavier Coudert <fxcoudert@gcc.gnu.org>
Date:   Mon Dec 27 01:13:59 2021 +0100

    LTO: Prune some warnings in the testsuite
    
    Warnings like:
    
        warning: using serial compilation of 2 LTRANS jobs
        warning: visibility attribute not supported in this configuration; ignored\[^\n\]*" $text "" text
    
    are pruned by lto.exp, but not for LTO testcases when run in other parts
    of the testsuite. They will be, now.
    
    gcc/testsuite/ChangeLog:
    
            PR testsuite/47334
            PR testsuite/103823
            * lib/prune.exp: Prune some warnings related to LTO and
            visibility.
    
    (cherry picked from commit 05edf6c470ae0ab50d42f16e78e476dbcc774842)

Diff:
---
 gcc/testsuite/lib/prune.exp | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gcc/testsuite/lib/prune.exp b/gcc/testsuite/lib/prune.exp
index 25fb98c6bed..c2ff05c2a37 100644
--- a/gcc/testsuite/lib/prune.exp
+++ b/gcc/testsuite/lib/prune.exp
@@ -92,6 +92,13 @@ proc prune_gcc_output { text } {
     # Ignore dsymutil warning (tool bug is actually linker)
     regsub -all "(^|\n)\[^\n\]*could not find object file symbol for symbol\[^\n\]*" $text "" text
 
+    # Ignore missing lto jobserver for tests that do more than 1 LTRANS unit
+    regsub -all "(^|\n)\[^\n\]*lto\[^\n\]*: warning: using serial compilation of \[^\n\]*" $text "" text
+    regsub -all "(^|\n)\[^\n\]*lto\[^\n\]*: note: see the \[^\n\]*'-flto' option documentation\[^\n\]* for more information" $text "" text
+
+    # Many tests that use visibility will still pass on platforms that don't support it.
+    regsub -all "(^|\n)\[^\n\]*lto1: warning: visibility attribute not supported in this configuration; ignored\[^\n\]*" $text "" text
+
     # If dg-enable-nn-line-numbers was provided, then obscure source-margin
     # line numbers by converting them to "NN" form.
     set text [maybe-handle-nn-line-numbers $text]

                 reply	other threads:[~2023-01-06  9:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230106091715.BA6A33858D33@sourceware.org \
    --to=marxin@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).