public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth.at.gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61407] Build errors on latest OS X 10.10 Yosemite with Xcode 6 on GCC 4.8.3
Date: Tue, 26 Aug 2014 19:39:00 -0000 [thread overview]
Message-ID: <bug-61407-4-SYK42mGXZU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61407-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407
--- Comment #30 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
The proposed changes in v4 of the patch aren't building here on 10.9. I don't
see how
# if defined(_DARWIN_FEATURE_64_BIT_INODE)
can completely substitute for…
# if ! defined(__DARWIN_64_BIT_INO_T) || __DARWIN_64_BIT_INO_T
as sys/cdefs.h shows…
/*
* _DARWIN_FEATURE_64_BIT_INODE indicates that the ino_t type is 64-bit, and
* structures modified for 64-bit inodes (like struct stat) will be used.
*/
#if __DARWIN_64_BIT_INO_T
#define _DARWIN_FEATURE_64_BIT_INODE 1
#endif
which means that…
# if defined(_DARWIN_FEATURE_64_BIT_INODE)
is effectively only
# if __DARWIN_64_BIT_INO_T
as the definition of _DARWIN_FEATURE_64_BIT_INODE only checks if
__DARWIN_64_BIT_INO_T is set and not if it is undefined as well.
>From gcc-bugs-return-459307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 26 19:40:13 2014
Return-Path: <gcc-bugs-return-459307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21492 invoked by alias); 26 Aug 2014 19:40:12 -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 21438 invoked by uid 55); 26 Aug 2014 19:40:09 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/58624] gcc internal compiler error: Segmentaion fault in insert_to_assembler_name_hash
Date: Tue, 26 Aug 2014 19:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
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-58624-4-56GXKkm32Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58624-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58624-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-08/txt/msg01804.txt.bz2
Content-length: 611
https://gcc.gnu.org/bugzilla/show_bug.cgi?idX624
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Tue Aug 26 19:39:36 2014
New Revision: 214543
URL: https://gcc.gnu.org/viewcvs?rev!4543&root=gcc&view=rev
Log:
PR c++/58624
* pt.c (tsubst_decl) [VAR_DECL]: Copy TLS model.
(tsubst_copy_and_build) [VAR_DECL]: Use TLS wrapper.
* semantics.c (finish_id_expression): Don't call TLS wrapper in a
template.
Added:
trunk/gcc/testsuite/g++.dg/tls/thread_local10.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/pt.c
trunk/gcc/cp/semantics.c
next prev parent reply other threads:[~2014-08-26 19:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 5:41 [Bug target/61407] New: " kassafari at gmail dot com
2014-06-04 5:54 ` [Bug target/61407] " pinskia at gcc dot gnu.org
2014-06-04 6:05 ` pinskia at gcc dot gnu.org
2014-06-04 7:21 ` kassafari at gmail dot com
2014-06-04 8:52 ` schwab@linux-m68k.org
2014-06-06 19:03 ` pinskia at gcc dot gnu.org
2014-06-06 19:06 ` pinskia at gcc dot gnu.org
2014-06-17 9:09 ` morpheby at gmail dot com
2014-06-17 9:48 ` manu at gcc dot gnu.org
2014-06-17 10:02 ` morpheby at gmail dot com
2014-06-20 12:27 ` egall at gwmail dot gwu.edu
2014-06-28 4:20 ` ericmark26 at gmail dot com
2014-07-20 16:24 ` dominyktiller at gmail dot com
2014-07-21 21:41 ` jrtc27 at jrtc27 dot com
2014-07-21 21:43 ` jrtc27 at jrtc27 dot com
2014-07-24 13:34 ` jrtc27 at jrtc27 dot com
2014-07-24 15:27 ` alexandermbock at gmail dot com
2014-07-31 2:12 ` alexandermbock at gmail dot com
2014-07-31 10:09 ` jrtc27 at jrtc27 dot com
2014-07-31 12:34 ` aggrostyle at gmail dot com
2014-08-02 16:12 ` ericmark26 at gmail dot com
2014-08-22 16:06 ` dominyktiller at gmail dot com
2014-08-25 18:17 ` jrtc27 at jrtc27 dot com
2014-08-26 16:05 ` jrtc27 at jrtc27 dot com
2014-08-26 17:28 ` howarth.at.gcc at gmail dot com
2014-08-26 18:18 ` jrtc27 at jrtc27 dot com
2014-08-26 19:39 ` howarth.at.gcc at gmail dot com [this message]
2014-08-26 20:41 ` morpheby at gmail dot com
2014-08-27 18:02 ` jrtc27 at jrtc27 dot com
2014-09-08 21:41 ` larryv at macports dot org
2014-09-09 5:08 ` larryv at macports dot org
2014-09-09 20:59 ` larryv at macports dot org
2014-09-10 0:36 ` larryv at macports dot org
2014-09-14 8:06 ` fxcoudert at gcc dot gnu.org
2014-09-29 18:41 ` fxcoudert at gcc dot gnu.org
2014-10-27 19:19 ` jeremyhu at macports dot org
2014-10-27 19:37 ` jeremyhu at macports dot org
2014-11-10 16:34 ` fxcoudert at gcc dot gnu.org
2014-11-10 20:27 ` fxcoudert at gcc dot gnu.org
2014-11-10 20:29 ` fxcoudert at gcc dot gnu.org
2014-11-11 2:01 ` jeremyhu at macports dot org
2014-11-11 8:18 ` fxcoudert at gcc dot gnu.org
2014-11-14 9:39 ` larryv at macports dot org
2014-11-15 14:26 ` derrick.k at gmx dot de
2014-11-15 14:54 ` fxcoudert at gcc dot gnu.org
2014-11-15 15:52 ` howarth at bromo dot med.uc.edu
2014-12-18 20:13 ` fxcoudert at gcc dot gnu.org
2021-08-07 1:15 ` 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-61407-4-SYK42mGXZU@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).