public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/47334] g++.dg/torture/pr31863.C -O2 -flto FAILs without visibility
Date: Fri, 06 Jan 2023 09:35:51 +0000	[thread overview]
Message-ID: <bug-47334-4-abzvH71esc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47334-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47334

--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:7097d2aafcae4b1cb89c28ff4fd4af18df9a2cef

commit r10-11152-g7097d2aafcae4b1cb89c28ff4fd4af18df9a2cef
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)

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 18:13 [Bug lto/47334] New: " ro at gcc dot gnu.org
2011-03-23 12:58 ` [Bug lto/47334] " ro at gcc dot gnu.org
2011-03-23 13:02 ` rguenther at suse dot de
2011-04-28 16:27 ` rguenth at gcc dot gnu.org
2013-11-27 13:20 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-12-24  8:36 ` [Bug middle-end/47334] " pinskia at gcc dot gnu.org
2021-12-26  1:52 ` pinskia at gcc dot gnu.org
2021-12-29 19:27 ` [Bug testsuite/47334] " fxcoudert at gcc dot gnu.org
2023-01-06  9:17 ` cvs-commit at gcc dot gnu.org
2023-01-06  9:35 ` cvs-commit at gcc dot gnu.org [this message]

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=bug-47334-4-abzvH71esc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).