public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/63344] [5 Regression] Linux (makeallyes config) compilation error: error: apic_numachip causes a section type conflict with numachip_system
Date: Wed, 24 Sep 2014 10:07:00 -0000	[thread overview]
Message-ID: <bug-63344-4-BOly36u1eT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63344-4@http.gcc.gnu.org/bugzilla/>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 2550 bytes --]

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

--- Comment #4 from Martin Liška <mliska at suse dot cz> ---
(In reply to Andi Kleen from comment #3)
> Yes it's a kernel bug. I hit it earlier too.
> 
> const always needs to go into separate sections.
> const __read_mostly is also meaningless.

Is there any existing bug in Linux Kernel that can be linked to this thread?
>From gcc-bugs-return-462415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Sep 24 10:10:00 2014
Return-Path: <gcc-bugs-return-462415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8822 invoked by alias); 24 Sep 2014 10:10:00 -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 8790 invoked by uid 48); 24 Sep 2014 10:09:56 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/63356] Compilation failure where clang does not have problems
Date: Wed, 24 Sep 2014 10:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
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: normal
X-Bugzilla-Who: trippels at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: attachments.created
Message-ID: <bug-63356-4-jOOFmPg0Az@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63356-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63356-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-09/txt/msg02249.txt.bz2
Content-length: 373

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc356

--- Comment #5 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Created attachment 33545
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id3545&actioníit
preprocessed testcase

Here's the unreduced testcase. I cannot reduce it, because
clang doesn't handle all the __builtin_ia32_bsrsi, etc. intrinsics.


  parent reply	other threads:[~2014-09-24 10:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63344-4@http.gcc.gnu.org/bugzilla/>
2014-09-23 15:18 ` pinskia at gcc dot gnu.org
2014-09-23 15:20 ` pinskia at gcc dot gnu.org
2014-09-24  4:04 ` andi-gcc at firstfloor dot org
2014-09-24 10:07 ` mliska at suse dot cz [this message]
2014-09-24 16:22 ` andi-gcc at firstfloor dot org
2014-09-25 20:44 ` mliska at suse dot cz

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-63344-4-BOly36u1eT@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).