public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ka_bena at yahoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67668] New: erroneous type argument for unary operator one's complement
Date: Mon, 21 Sep 2015 12:24:00 -0000 [thread overview]
Message-ID: <bug-67668-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67668
Bug ID: 67668
Summary: erroneous type argument for unary operator one's
complement
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: ka_bena at yahoo dot fr
Target Milestone: ---
int main(void)
{
~( 1. + 0.i ) ;
~(1.) ;
return 0 ;
}
/* Results::
main_cmp1_err.c:4:3: attention : statement with no effect [-Wunused-value]
~( 1. + 0.i ) ;
^
main_cmp1_err.c:5:3: erreur: type d'argument erroné pour un complément de
bit
~(1.) ;
^
Comment:: ( 1. + 0.i ) must be an erroneous type argument for ~ .
Microsoft Windows XP Profesional version2002 Service Pack 3.
Gcc 4.8.0 win32 mingw32
*/
>From gcc-bugs-return-497725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 21 12:29:29 2015
Return-Path: <gcc-bugs-return-497725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32157 invoked by alias); 21 Sep 2015 12:29:29 -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 32097 invoked by uid 48); 21 Sep 2015 12:29:25 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67668] erroneous type argument for unary operator one's complement
Date: Mon, 21 Sep 2015 12:29: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.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
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:
Message-ID: <bug-67668-4-JmGyKuDRdY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67668-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-09/txt/msg01703.txt.bz2
Content-length: 181
https://gcc.gnu.org/bugzilla/show_bug.cgi?idg668
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 67667 has been marked as a duplicate of this bug. ***
next reply other threads:[~2015-09-21 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 12:24 ka_bena at yahoo dot fr [this message]
2015-09-21 12:44 ` [Bug c/67668] " glisse at gcc dot gnu.org
2015-09-22 16:51 ` ka_bena at yahoo dot fr
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-67668-4@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).