https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|rask at gcc dot gn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
Ivan Sorokin changed:
What|Removed |Added
CC||vanyacpp at gmail dot com
--- Comment #60
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
Joseph C. Sible changed:
What|Removed |Added
CC||josephcsible at gmail dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #58 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #57 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #56 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #55 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #54 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #53 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #52 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #51 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #50 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #49 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #48 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #47 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #46 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #45 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #44 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #43 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #42 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #41 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #40 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #39 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #38 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #37 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #36 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #35 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #34 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #33 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #32 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #31 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #30 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #29 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #28 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #27 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #26 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #25 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #24 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #23 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #22 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #21 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #20 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #19 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #18 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #17 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #16 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #15 from owner at bugs dot debian.org ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message has
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
--- Comment #14 from owner at bugs dot debian.org 2012-07-10 10:54:26 UTC ---
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been recei
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
Daniel Santos changed:
What|Removed |Added
CC||daniel.santos at pobox dot
--- Comment #12 from bonzini at gnu dot org 2007-11-29 11:43 ---
I think this should use find_comparison_args.
--
bonzini at gnu dot org changed:
What|Removed |Added
--- Comment #11 from rask at gcc dot gnu dot org 2007-11-29 00:09 ---
In reply to comment #10 from Steven Bosscher 2007-11-28 22:02:
> > + for (defs = DF_INSN_DEFS (insn);
> > + *defs && DF_REF_REGNO (*defs) != REGNO (x);
> > + defs++)
> > +;
> Are you aware of df_find
--- Comment #10 from steven at gcc dot gnu dot org 2007-11-28 22:02 ---
> + for (defs = DF_INSN_DEFS (insn);
> + *defs && DF_REF_REGNO (*defs) != REGNO (x);
> + defs++)
> +;
Are you aware of df_find_def() ?
> + if (minus_elt)
> + cmp = cse_find_compari
--- Comment #9 from rask at gcc dot gnu dot org 2007-11-28 18:01 ---
Created an attachment (id=14657)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14657&action=view)
Patch v2 to enhance cse.c
This patch also handles unsigned comparisons and thus optimizes the original
testcase to
--- Comment #8 from rask at gcc dot gnu dot org 2007-11-27 18:04 ---
Created an attachment (id=14647)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14647&action=view)
Patch to enhance cse.c
The attached patch can optimize this testcase:
void foo (int);
int bar2 (int a, int b)
{
--
rask at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |rask at gcc dot gnu dot org
|dot org
--- Comment #7 from eweddington at cso dot atmel dot com 2007-08-23 20:10
---
Confirmed for AVR. GCC 4.2.1 for avr generates this:
foo:
/* prologue: frame size=0 */
push r14
push r15
push r16
push r17
/* prologue end (size=4) */
movw r14,r22
56 matches
Mail list logo
