public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pefoley2 at pefoley dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/80922] #pragma diagnostic ignored not honoured with -flto
Date: Sat, 21 Jan 2023 05:59:17 +0000 [thread overview]
Message-ID: <bug-80922-4-K733gIrdsq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80922-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80922
pefoley2 at pefoley dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pefoley2 at pefoley dot com
--- Comment #8 from pefoley2 at pefoley dot com ---
Note that this appears to be affecting the gcc source tree.
Attempting a build with --with-build-config=bootstrap-lto --enable-werror
errors out with:
In function ‘release’,
inlined from ‘release’ at ../../gcc/vec.h:1915:0,
inlined from ‘__dt_base ’ at ../../gcc/vec.h:1574:0,
inlined from ‘visit_reference_op_call.isra’ at
../../gcc/tree-ssa-sccvn.cc:5562:0:
../../gcc/vec.h:316: error: ‘free’ called on unallocated object ‘accesses’
[-Werror=free-nonheap-object]
316 | ::free (v);
|
../../gcc/tree-ssa-sccvn.cc: In function ‘visit_reference_op_call.isra’:
../../gcc/tree-ssa-sccvn.cc:5457: note: declared here
5457 | auto_vec<ao_ref, accesses_limit> accesses;
|
lto1: all warnings being treated as errors
Due to this pragma being ignored:
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/vec.h;h=a536b68732ddcb9ed7b223803308b3e079a53969;hb=HEAD#l300
next prev parent reply other threads:[~2023-01-21 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-80922-4@http.gcc.gnu.org/bugzilla/>
2021-02-14 23:24 ` msebor at gcc dot gnu.org
2021-02-14 23:28 ` msebor at gcc dot gnu.org
2021-02-15 8:16 ` marxin at gcc dot gnu.org
2022-04-21 9:29 ` marxin at gcc dot gnu.org
2023-01-21 5:59 ` pefoley2 at pefoley dot com [this message]
2023-01-21 6:17 ` pinskia at gcc dot gnu.org
2023-01-23 4:33 ` pefoley2 at pefoley dot com
2023-03-31 11:56 ` marxin at gcc dot gnu.org
2023-05-20 11:08 ` amonakov at gcc dot gnu.org
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-80922-4-K733gIrdsq@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).