Bug 19204 - [m68k] pea can force reloads that cause inefficient code
Summary: [m68k] pea can force reloads that cause inefficient code
Status: RESOLVED INVALID
Alias: None
Product: gcc
Classification: Unclassified
Component: target (show other bugs)
Version: unknown
: P2 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-30 12:19 UTC by Steven Bosscher
Modified: 2016-04-24 22:22 UTC (History)
3 users (show)

See Also:
Host:
Target: m68k
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-06-19 14:49:24


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steven Bosscher 2004-12-30 12:19:41 UTC
Item 85 from the old PROBLEMS file (no test case available):

----------------------------------------
pea can force a value to be reloaded into an areg which
can make it worse than separate adding and pushing.  This can only
happen for adding something within addql range and it only loses if
the qty becomes dead at that point so it can be added to with no
copying.
----------------------------------------
Comment 1 Andrew Pinski 2005-06-19 14:49:24 UTC
Confirmed.
Comment 2 Steven Bosscher 2010-02-12 22:02:01 UTC
Waiting for a m68k maintainer to do something here...
Comment 3 Steven Bosscher 2010-02-12 22:02:33 UTC
Waiting for a m68k maintainer to do something here...
Comment 4 Steven Bosscher 2011-02-25 23:13:04 UTC
No response from m68k maintainers for more than 5 years. That may be a record.
This just clutters my bug searches. WONTFIX seems the most logical "way out".
Comment 5 Andreas Schwab 2011-02-25 23:58:10 UTC
Not a reason to close them.
Comment 6 Steven Bosscher 2011-02-26 00:17:55 UTC
Also fine, not closed. Great to see that you pay enough attention to stop the reporter from closing his own PRs. I wish you would be just as fast with actually doing something about them. It is not even clear whether these problems still exist!

If this still not OK with you, I suggest you do something about these 15+ years old problems, or close these and re-file under your own account. They may not bother you but I don't want them anymore in my list.
Comment 7 Jeffrey A. Law 2016-04-24 22:22:12 UTC
A bug like this without a testcase is pointless.  Even more so when it's specific to a dead target.

Andreas may not like closing, but it's the right thing to do.  Obviously if someone comes up with a testcase, then a new bug can be opened and handled appropriately.