public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65886] [5/6 Regression] Copy reloc in PIE incompatible with DSO created by -Wl,-Bsymbolic Date: Sat, 25 Apr 2015 17:37:00 -0000 [thread overview] Message-ID: <bug-65886-4-O756gIeNpK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65886-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65886 --- Comment #10 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Thiago Macieira from comment #7) > (In reply to H.J. Lu from comment #4) > > (In reply to Thiago Macieira from comment #3) > > > Thanks H.J.! > > > > > > Can I ask that -fsymbolic be the default? Otherwise, code with -fPIE MUST > > > add -fsymbolic in GCC 5+, but can't add it prior because the option didn't > > > exist. Please leave that for a release or two so that we can adapt > > > > Linux kernel has things like > > > > M16_CFLAGS := $(call cc-option, -m16, $(CODE16GCC_CFLAGS)) > > > > It adds -m16 only if it exits. Why can't KDE do something like this? > > There are many ways to achieve it and it works with all compilers. > > We can. The problem is not the ability, it's the need to do it. Now, you have a need :-). > No buildsystem currently has support for -fsymbolic, since it doesn't exist > yet. However, the lack of such option will produce subtle bugs. I'm asking > for a grace period until the changes propagate. > I don't think GCC default should cater shared libraries which aren't psABI compliant. It is the risk you take when using a non-psABI compliant library. >From gcc-bugs-return-484644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Apr 25 17:41:39 2015 Return-Path: <gcc-bugs-return-484644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 63285 invoked by alias); 25 Apr 2015 17:41:39 -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 63242 invoked by uid 48); 25 Apr 2015 17:41:35 -0000 From: "frankhb1989 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65890] New: [C++03]sizeof(qualified-id) accepted when the operand denotes a non-static member Date: Sat, 25 Apr 2015 17:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: frankhb1989 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: <bug-65890-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: 2015-04/txt/msg02196.txt.bz2 Content-length: 761 https://gcc.gnu.org/bugzilla/show_bug.cgi?ide890 Bug ID: 65890 Summary: [C++03]sizeof(qualified-id) accepted when the operand denotes a non-static member Product: gcc Version: 4.9.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: frankhb1989 at gmail dot com Target Milestone: --- Case: struct Tag { int m; }; int main() { sizeof(&(Tag::m)); } According to ISO C++03 5.1/10, this is not well-formed. (But C++11 should work.) However, G++ 4.9.1 wrongly accepted it even with -std=c++03 -pedantic-errors. (I have no GCC 5 distro so have not tested it.)
next prev parent reply other threads:[~2015-04-25 17:37 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-25 13:45 [Bug target/65886] New: [5/6 Regression] External reference in PIE to DSO created with -Wl,-Bsymbolic hjl.tools at gmail dot com 2015-04-25 13:46 ` [Bug target/65886] " hjl.tools at gmail dot com 2015-04-25 15:47 ` [Bug target/65886] [5/6 Regression] External reference in PIE incompatible with DSO created by -Wl,-Bsymbolic hjl.tools at gmail dot com 2015-04-25 16:33 ` hjl.tools at gmail dot com 2015-04-25 16:51 ` [Bug target/65886] [5/6 Regression] Copy reloc " thiago at kde dot org 2015-04-25 17:06 ` hjl.tools at gmail dot com 2015-04-25 17:08 ` hjl.tools at gmail dot com 2015-04-25 17:25 ` hjl.tools at gmail dot com 2015-04-25 17:30 ` thiago at kde dot org 2015-04-25 17:37 ` hjl.tools at gmail dot com [this message] 2015-04-25 17:42 ` hjl.tools at gmail dot com 2015-04-27 9:05 ` rguenth at gcc dot gnu.org 2015-04-27 12:14 ` jakub at gcc dot gnu.org 2015-04-27 12:22 ` hjl.tools at gmail dot com 2015-04-27 12:37 ` jakub at gcc dot gnu.org 2015-04-27 12:44 ` hjl.tools at gmail dot com 2015-04-27 13:14 ` hjl.tools at gmail dot com 2015-04-27 13:51 ` jakub at gcc dot gnu.org 2015-04-27 19:18 ` thiago at kde dot org 2015-04-29 19:05 ` hjl.tools at gmail dot com 2015-04-29 19:06 ` hjl.tools at gmail dot com 2015-05-05 15:03 ` thiago at kde dot org 2015-05-05 15:09 ` hjl.tools at gmail dot com 2015-05-05 15:12 ` jakub at gcc dot gnu.org 2015-05-05 15:14 ` jakub at gcc dot gnu.org 2015-05-05 15:38 ` hjl.tools at gmail dot com 2015-05-05 15:47 ` jakub at gcc dot gnu.org 2015-05-05 15:48 ` thiago at kde dot org 2015-05-05 15:54 ` thiago at kde dot org 2015-06-30 10:32 ` rguenth at gcc dot gnu.org 2015-07-16 9:17 ` rguenth at gcc dot gnu.org 2015-08-06 18:06 ` thiago at kde dot org 2015-08-06 18:24 ` hjl.tools at gmail dot com 2015-08-06 18:27 ` thiago at kde dot 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-65886-4-O756gIeNpK@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).