This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/13472] [3.3 Regression] optimizer generates code to store data in const int, resulting in a segfault
- From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Jan 2004 08:36:14 -0000
- Subject: [Bug optimization/13472] [3.3 Regression] optimizer generates code to store data in const int, resulting in a segfault
- References: <20031223020924.13472.p.van-hoof@qub.ac.uk>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-01-21 08:35 -------
> I don't understand this part of your comment.
Until early January, bugfixes on the 3.3 branch had been very localized, either
in a specific back-end or front-end or optimization pass that can be disabled.
Then, suddendly, central parts of the compiler that are run at any optimization
levels started to be touched:
- I think Richard's patch has a potential effect on every memory pattern in
every back-end,
- Joern's reload patch is... a reload patch and, judging by him asking you to
put his other reload patch (fix for PR 11864) to the branch, this latter patch
having a serious impact on the back-end (Alpha, PA, MIPS and SPARC at least),
I'm not sure that he fully evaluated the impact of this patch,
- Jan's patch deals with a very hot topic: table jump removal. We have been
fighting this problem for a long time and I was under the impression it is more
or less under control on the 3.3 branch.
> Do you see similar disaster on branch?
No.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13472