public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominyktiller 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: Sun, 20 Jul 2014 16:24:00 -0000 [thread overview]
Message-ID: <bug-61407-4-TuCvaOcEca@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61407-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: 6626 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61407
Dominyk Tiller <dominyktiller at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominyktiller at gmail dot com
--- Comment #13 from Dominyk Tiller <dominyktiller at gmail dot com> ---
This remains an issue on the latest release of 4.9.1 -
xgcc: warning: couldn’t understand kern.osversion ‘14.0.0
In file included from /usr/include/stdio.h:65:0,
from ../../.././libgcc/../gcc/tsystem.h:87,
from ../../.././libgcc/libgcc2.c:27:
/usr/include/Availability.h:174:44: error: missing binary operator before token
"("
#if defined(__has_feature) &&
__has_feature(attribute_availability_with_message)
^
In file included from /usr/include/stdio.h:65:0,
from ../../.././libgcc/../gcc/tsystem.h:87,
from ../../.././libgcc/libgcc2.c:27:
/usr/include/Availability.h:184:44: error: missing binary operator before token
"("
#if defined(__has_feature) &&
__has_feature(attribute_availability_app_extension)
^
make[5]: *** [_muldi3.o] Error 1
make[4]: *** [multi-do] Error 1
make[3]: *** [all-multi] Error 2
make[2]: *** [all-stage1-target-libgcc] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [all] Error 2
The patch provided on 4.8.3 also doesn't apply to 4.9.1, which was pretty much
expected. Is there status/timeline for folding in 10.10 support?
>From gcc-bugs-return-456809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 20 17:00:06 2014
Return-Path: <gcc-bugs-return-456809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28120 invoked by alias); 20 Jul 2014 17:00:04 -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 27580 invoked by uid 48); 20 Jul 2014 16:59:53 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/61854] Warning single-line comment for -stdÈ9?
Date: Sun, 20 Jul 2014 17:00: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.10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-61854-4-pqIdP2ZjgA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-07/txt/msg01400.txt.bz2
Content-length: 680
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61854
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-07-20
CC| |manu at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Perhaps GCC should accept // without comment unless -Wpedantic. The current
error is nonsensical.
>From gcc-bugs-return-456810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jul 20 17:36:00 2014
Return-Path: <gcc-bugs-return-456810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19481 invoked by alias); 20 Jul 2014 17:35:59 -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 18828 invoked by uid 48); 20 Jul 2014 17:35:48 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61632] Memory corruption on error when writing formatted data
Date: Sun, 20 Jul 2014 17:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-61632-4-IjzGhyuCSi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61632-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61632-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-07/txt/msg01401.txt.bz2
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida632
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #33155|0 |1
is obsolete| |
--- Comment #21 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Created attachment 33160
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id3160&actioníit
Updated patch taking care of valgrind error
This patch includes fixing the valgrind error by allocating and setting the
NULL byte at the end of the format string.
next prev parent reply other threads:[~2014-07-20 16:24 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 [this message]
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
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-TuCvaOcEca@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).