public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60520] stack adjustment are not merged anymore
Date: Fri, 14 Mar 2014 08:49:00 -0000	[thread overview]
Message-ID: <bug-60520-4-dTcWbEuSrM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60520-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60520

--- Comment #7 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #6)
> Furthermore, it is already fixed since r208551.

Indeed, the fix for PR57320 also fixed this one.
>From gcc-bugs-return-446266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 08:53:26 2014
Return-Path: <gcc-bugs-return-446266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11697 invoked by alias); 14 Mar 2014 08:53:26 -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 11680 invoked by uid 48); 14 Mar 2014 08:53:22 -0000
From: "david at westcontrol dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/60523] New: Warning flag for octal literals
Date: Fri, 14 Mar 2014 08:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: david at westcontrol dot com
X-Bugzilla-Status: UNCONFIRMED
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_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-60523-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-03/txt/msg01135.txt.bz2
Content-length: 1308

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`523

            Bug ID: 60523
           Summary: Warning flag for octal literals
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: david at westcontrol dot com

It would be nice if there were a warning flag that triggered on octal literals.

Octal literals are rarely used in modern C and C++ code, but can easily be
introduced by mistake - "int x = 050;" appears at first reading to set x to 50,
but in C and C++ the leading 0 means it is interpreted as octal and therefore
sets x to 40 (decimal).

As octal literals are seldom useful, and often confusing or accidental, they
are banned by coding standards like MISRA.  But as they are part of the
language defined by the C and C++ standards, and are used in some existing
code, they obviously cannot be removed.  As a compromise, I would like to
propose the introduction of a warning flags "-Woctal" which would produce a
diagnostic message when a literal is interpreted as an octal number.  Of
preference, this would be included in "-Wextra" (it probably should not be in
"-Wall", since octal literals are valid C and C++).


  parent reply	other threads:[~2014-03-14  8:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 21:26 [Bug target/60520] New: " ubizjak at gmail dot com
2014-03-13 21:41 ` [Bug target/60520] " hjl.tools at gmail dot com
2014-03-13 22:02 ` hjl.tools at gmail dot com
2014-03-13 22:22 ` hjl.tools at gmail dot com
2014-03-14  5:14 ` hjl.tools at gmail dot com
2014-03-14  8:03 ` rguenth at gcc dot gnu.org
2014-03-14  8:27 ` jakub at gcc dot gnu.org
2014-03-14  8:49 ` ubizjak at gmail dot com [this message]
2014-03-14  8:59 ` ubizjak at gmail dot com
2014-03-14 15:45 ` hjl.tools at gmail dot com
2014-03-14 16:20 ` jakub at gcc dot gnu.org
2014-03-14 20:33 ` hjl.tools at gmail dot com
2014-03-19 21:56 ` hjl.tools at gmail dot com

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-60520-4-dTcWbEuSrM@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).