public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60517] warning/error for taking address of member of a temporary object
Date: Fri, 14 Mar 2014 16:51:00 -0000	[thread overview]
Message-ID: <bug-60517-4-cNZ09hASqr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60517-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #6)
> (In reply to Marc Glisse from comment #5)
> > I would need a different (middle-end) warning that
> > detects return &local_var,
> 
> To confirm this, I looked at the last dangling reference I debugged,
> recompiled it with -O3 -fkeep-inline-functions, and a grep for "return &" in
> the .optimized dump showed:
>   return &one;
>   return &one;
>   return &D.495451.c_;
> (where "one" is a global variable, but D.495451 is a local variable)
> so even this trivial version of the warning would be useful.

To avoid duplicates, the front-end could just return something else, like NULL,
when it detects this case (I guess the behavior is undefined and we can do
whatever we want, no?).
>From gcc-bugs-return-446309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Mar 14 16:59:23 2014
Return-Path: <gcc-bugs-return-446309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25017 invoked by alias); 14 Mar 2014 16:59:23 -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 24969 invoked by uid 48); 14 Mar 2014 16:59:20 -0000
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60528] New: MIPS GCC puts out complex constant incorrectly when in big-endian mode
Date: Fri, 14 Mar 2014 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sje at gcc dot gnu.org
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 cc cf_gcctarget
Message-ID: <bug-60528-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/msg01178.txt.bz2
Content-length: 1510

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

            Bug ID: 60528
           Summary: MIPS GCC puts out complex constant incorrectly when in
                    big-endian mode
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: sje at gcc dot gnu.org
                CC: rsandifo at gcc dot gnu.org
            Target: mips-*-*

The included test program prints out:

x = 0.634964 1.298458
x = inf inf

on MIPS instead of:

x = 0.634964 1.298458
x = 0.182506 1.163916

To reproduce the problem you need to compile the program with no optimization
(-O0) and in big-endian mode.  Little endian mode seems fine.  When I compare
the assembly language output to an earlier 4.8.1 GCC, the latest GCC output
contains the following code to store the complex constant passed in to csinh:

$LC0:
    .word    1071927711
    .word    3624173458
    .word    1073006203
    .word    1962331215

Earlier GCC compilers that worked contained:

$LC0:
    .word    1071927711
    .word    -670793838
    .word    1073006203
    .word    1962331215


Test case:

#include <stdio.h>
#include <complex.h>
#include <math.h>

int main()
{
    double complex x;
    x = 0.63496391478473613 + 1.2984575814159773I;
    printf("x = %f %f\n", creal(x), cimag(x));
    x = csinh(x);
    printf("x = %f %f\n", creal(x), cimag(x));
    return 0;
}


  parent reply	other threads:[~2014-03-14 16:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 15:54 [Bug c++/60517] New: " manu at gcc dot gnu.org
2014-03-13 20:42 ` [Bug c++/60517] " glisse at gcc dot gnu.org
2014-03-13 23:44 ` manu at gcc dot gnu.org
2014-03-14  7:19 ` glisse at gcc dot gnu.org
2014-03-14 10:41 ` manu at gcc dot gnu.org
2014-03-14 12:13 ` glisse at gcc dot gnu.org
2014-03-14 15:41 ` glisse at gcc dot gnu.org
2014-03-14 16:51 ` manu at gcc dot gnu.org [this message]
2014-03-14 17:29 ` glisse at gcc dot gnu.org
2014-03-14 18:02 ` glisse at gcc dot gnu.org
2014-04-05 23:01 ` glisse at gcc dot gnu.org
2014-04-06  8:23 ` glisse at gcc dot gnu.org
2014-04-06 10:17 ` glisse at gcc dot gnu.org
2014-06-26 17:22 ` paolo.carlini at oracle dot com
2014-07-31  9:34 ` glisse at gcc dot gnu.org
2014-08-22 13:02 ` manu at gcc dot gnu.org
2014-08-22 13:22 ` glisse at gcc dot gnu.org
2014-11-22 14:48 ` glisse 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-60517-4-cNZ09hASqr@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).