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 target/95229] [11 Regression] in mark_jump_label_1 Date: Thu, 21 May 2020 12:21:52 +0000 [thread overview] Message-ID: <bug-95229-4-4rayfdk9Bq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95229-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95229 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:2f20c7040f884b542cadf46fd77188729ab3cb17 commit r11-548-g2f20c7040f884b542cadf46fd77188729ab3cb17 Author: Martin Liska <mliska@suse.cz> Date: Thu May 21 14:21:31 2020 +0200 Fix a test-case warning. PR target/95229 * g++.target/i386/pr95229.C: Fix error: unnamed type with no linkage used to declare variable â<unnamed class> eâ with linkage with -std=gnu++98.
next prev parent reply other threads:[~2020-05-21 12:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-20 8:16 [Bug c++/95229] New: ice " dcb314 at hotmail dot com 2020-05-20 8:37 ` [Bug middle-end/95229] " pinskia at gcc dot gnu.org 2020-05-20 8:41 ` dcb314 at hotmail dot com 2020-05-20 8:50 ` marxin at gcc dot gnu.org 2020-05-20 8:51 ` [Bug middle-end/95229] [11 Regression] " marxin at gcc dot gnu.org 2020-05-20 12:13 ` [Bug target/95229] " rguenth at gcc dot gnu.org 2020-05-20 12:20 ` rguenth at gcc dot gnu.org 2020-05-20 12:24 ` rguenth at gcc dot gnu.org 2020-05-20 13:28 ` ubizjak at gmail dot com 2020-05-20 17:01 ` cvs-commit at gcc dot gnu.org 2020-05-21 12:21 ` cvs-commit at gcc dot gnu.org [this message] 2020-05-21 18:17 ` ubizjak at gmail dot com
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-95229-4-4rayfdk9Bq@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: linkBe 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).