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 other/61146] wide-int error when building GCC with clang
Date: Wed, 28 May 2014 18:40:00 -0000 [thread overview]
Message-ID: <bug-61146-4-DFFMTLM6mY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61146-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61146
Jack Howarth <howarth.at.gcc at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |howarth.at.gcc at gmail dot com
--- Comment #12 from Jack Howarth <howarth.at.gcc at gmail dot com> ---
(In reply to mrs@gcc.gnu.org from comment #11)
> Yes, weird, thanks.
A find that gcc trunk at r211023 bootstrap fines against the clang 3.4svn-based
compilers from Xcode 5.1.1. However I am still puzzled why, considering that it
is agreed that the casts are useless and ignored by gcc, why they weren't just
removed? I did find that freebsd has been doing this…
http://svnweb.freebsd.org/base/head/contrib/gcc/longlong.h?view=patch&r1=211505&r2=211504&pathrev=211505
>From gcc-bugs-return-452749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 28 18:48:05 2014
Return-Path: <gcc-bugs-return-452749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10490 invoked by alias); 28 May 2014 18:48: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 10291 invoked by uid 48); 28 May 2014 18:47:59 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/61146] wide-int error when building GCC with clang
Date: Wed, 28 May 2014 18:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
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-61146-4-8fVqOwORe7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61146-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61146-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-05/txt/msg02441.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?ida146
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Because they are not ignored and are not useless.
next prev parent reply other threads:[~2014-05-28 18:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 18:47 [Bug other/61146] New: " olegendo at gcc dot gnu.org
2014-05-11 18:54 ` [Bug other/61146] " pinskia at gcc dot gnu.org
2014-05-11 19:37 ` pinskia at gcc dot gnu.org
2014-05-11 19:48 ` glisse at gcc dot gnu.org
2014-05-27 20:36 ` mrs at gcc dot gnu.org
2014-05-27 20:37 ` mrs at gcc dot gnu.org
2014-05-27 20:43 ` mrs at gcc dot gnu.org
2014-05-28 16:18 ` fxcoudert at gcc dot gnu.org
2014-05-28 17:00 ` mrs at gcc dot gnu.org
2014-05-28 17:06 ` dominiq at lps dot ens.fr
2014-05-28 18:40 ` howarth.at.gcc at gmail dot com [this message]
2014-05-28 18:50 ` dominiq at lps dot ens.fr
2014-05-28 18:52 ` mikestump at comcast dot net
2014-05-28 19:09 ` howarth.at.gcc at gmail dot com
2014-05-28 19:37 ` manu at gcc dot gnu.org
2014-05-28 20:02 ` mikestump at comcast dot net
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-61146-4-DFFMTLM6mY@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).