public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14541] [tree-ssa] built-in math functions are not fully optimized at tree level
Date: Mon, 08 Dec 2014 10:32:00 -0000	[thread overview]
Message-ID: <bug-14541-4-7oIm1CKYMU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-14541-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: 3604 bytes --]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14541

--- Comment #20 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 8 Dec 2014, ktkachov at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=14541
> 
> ktkachov at gcc dot gnu.org changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |ktkachov at gcc dot gnu.org
> 
> --- Comment #19 from ktkachov at gcc dot gnu.org ---
> (In reply to Richard Biener from comment #18)
> > Author: rguenth
> > Date: Wed Dec  3 11:55:14 2014
> > New Revision: 218308
> > 
> > URL: https://gcc.gnu.org/viewcvs?rev=218308&root=gcc&view=rev
> > Log:
> > 2014-12-03  Richard Biener  <rguenther@suse.de>
> > 
> > 	PR middle-end/14541
> > 	* builtins.c (fold_builtin_logarithm): Implement simplifications ...
> > 	* match.pd: ... here as patterns.
> > 
> > Modified:
> >     trunk/gcc/ChangeLog
> >     trunk/gcc/builtins.c
> >     trunk/gcc/match.pd
> 
> With this commit the builtin-explog-1.c test stops folding the builtins on
> aarch64 (and consequently FAILs)

Which one exactly?  That is, what is the failing link output?
>From gcc-bugs-return-469705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 08 10:37:00 2014
Return-Path: <gcc-bugs-return-469705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26341 invoked by alias); 8 Dec 2014 10:37:00 -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 26278 invoked by uid 48); 8 Dec 2014 10:36:56 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14541] [tree-ssa] built-in math functions are not fully optimized at tree level
Date: Mon, 08 Dec 2014 10:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: tree-ssa
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-14541-4-cH13ukDQJ1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-14541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-14541-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-12/txt/msg00712.txt.bz2
Content-length: 461

https://gcc.gnu.org/bugzilla/show_bug.cgi?id\x14541

--- Comment #21 from ktkachov at gcc dot gnu.org ---
Created attachment 34215
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id4215&actioníit
Link errors output for aarch64

> Which one exactly?  That is, what is the failing link output?

All of them AFAICS. I'm attaching the link failures log.

The test PASSes at -O2 -flto and -O2 -flto -flto-partition=none

but FAILs on all other torture options


  parent reply	other threads:[~2014-12-08 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-14541-4@http.gcc.gnu.org/bugzilla/>
2012-02-12  9:24 ` pinskia at gcc dot gnu.org
2014-10-31  4:01 ` pinskia at gcc dot gnu.org
2014-12-01 14:15 ` rguenth at gcc dot gnu.org
2014-12-02 11:23 ` rguenth at gcc dot gnu.org
2014-12-03 11:55 ` rguenth at gcc dot gnu.org
2014-12-08 10:28 ` ktkachov at gcc dot gnu.org
2014-12-08 10:32 ` rguenther at suse dot de [this message]
2014-12-11 13:14 ` rguenth at gcc dot gnu.org
2014-12-11 13:30 ` ktkachov at gcc dot gnu.org
2014-12-15 13:11 ` rguenth at gcc dot gnu.org
     [not found] <bug-14541-5009@http.gcc.gnu.org/bugzilla/>
2006-11-26  8:15 ` pinskia at gcc dot gnu dot org
     [not found] <20040312001701.14541.kazu@gcc.gnu.org>
2005-07-12 21:26 ` pinskia at gcc dot gnu dot org
2004-03-12  0:17 [Bug optimization/14541] New: [tree-ssa] gcc.dg/torture/builtin-explog-1.c fails kazu at cs dot umass dot edu
2004-05-24 21:48 ` [Bug tree-optimization/14541] [tree-ssa] built-in math functions are not fully optimized at tree level pinskia at gcc dot gnu dot org
2004-06-01  1:47 ` pinskia at gcc dot gnu dot org
2004-06-21  5:15 ` pinskia at gcc dot gnu dot 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-14541-4-7oIm1CKYMU@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).