public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48026] #pragma optimize ignored for C++
Date: Wed, 17 Dec 2014 12:56:00 -0000 [thread overview]
Message-ID: <bug-48026-4-7s2OpuKUOL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48026-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48026
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
This is probably because the preprocessor runs before the #pragmas are handled.
If so, this is the same issue as for #pragma GCC diagnostics in C++ (PR53431).
>From gcc-bugs-return-470986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Dec 17 13:07:02 2014
Return-Path: <gcc-bugs-return-470986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1520 invoked by alias); 17 Dec 2014 13:07:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1457 invoked by uid 48); 17 Dec 2014 13:06:58 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64336] Template functions are not instrumented at -O0 and -Og
Date: Wed, 17 Dec 2014 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64336-4-bEIKMHBHtC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64336-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64336-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-12/txt/msg01993.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?idd336
--- Comment #3 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Yes, this patch seems to work...
But why did this only cause problems with template expansions and nothing else
?
next prev parent reply other threads:[~2014-12-17 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 19:44 [Bug c++/48026] New: " sam at robots dot org.uk
2012-02-02 6:25 ` [Bug c++/48026] " pinskia at gcc dot gnu.org
2012-07-25 12:40 ` linux at carewolf dot com
2014-12-10 17:33 ` f.boesing at gmx dot de
2014-12-17 12:56 ` manu at gcc dot gnu.org [this message]
2023-12-06 8:31 ` [Bug c++/48026] #pragma optimize ignored for C++ for preprocessor gb.devel at gmail dot com
2023-12-06 8:33 ` sjames at gcc dot gnu.org
2023-12-06 8:35 ` sjames at gcc dot gnu.org
2024-03-18 0:32 ` pinskia 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-48026-4-7s2OpuKUOL@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).