public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66916] New: [6 Regression] FAIL: gcc.target/arm/pr43920-2.c object-size text <= 54
Date: Fri, 17 Jul 2015 17:10:00 -0000 [thread overview]
Message-ID: <bug-66916-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66916
Bug ID: 66916
Summary: [6 Regression] FAIL: gcc.target/arm/pr43920-2.c
object-size text <= 54
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: ktkachov at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Build: arm*
Created attachment 36006
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36006&action=edit
Failing assembly
After this commit I'm seeing the test fail on arm targets:
Author: rguenth <rguenth@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Thu Jul 16 08:28:51 2015 +0000
2015-07-16 Richard Biener <rguenther@suse.de>
* fold-const.c (fold_widened_comparison): Remove.
(fold_sign_changed_comparison): Likewise.
(fold_comparison): Move widened and sign-changed comparison
simplification ...
* match.pd: ... to patterns here.
* generic-match-head.c: Include target.h.
* gimple-match-head.c: Likewise.
* gcc.dg/tree-ssa/pr21031.c: Adjust.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225861
138bc75d-0d04-0410-961f-82ee72b054a4
a sub+cmp sequence is not merged into a subs, causing the code size regression
next reply other threads:[~2015-07-17 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 17:10 ktkachov at gcc dot gnu.org [this message]
2015-07-17 17:11 ` [Bug middle-end/66916] " ktkachov at gcc dot gnu.org
2015-07-21 8:02 ` rguenth at gcc dot gnu.org
2015-07-22 9:49 ` rguenth at gcc dot gnu.org
2015-07-23 7:30 ` rguenth at gcc dot gnu.org
2015-07-23 7:30 ` rguenth 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-66916-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).