This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 11/19/2015 10:48 AM, Manuel LÃpez-IbÃÃez wrote:
Right. THe problem is there wasn't any real information on how that affected code generation.On 19 November 2015 at 17:09, Jeff Law <law@redhat.com> wrote:The even longer term direction for this code is to separate out the type-limits warning from the canonicalization and shortening. I've got a blob of code form Kai that goes in that direction, but it needs more engineering around it. Ideally the canonicalization/shortening moves into match.pd. The warning, in theory, moves out of the front-ends as well.The last attempt by Kai was here: https://gcc.gnu.org/ml/gcc-patches/2015-09/msg01265.html
On hold pending fixing the type-limits warning placement. Essentially that has to be untangled first.But there were a couple of patches from you some time ago, for example: http://permalink.gmane.org/gmane.comp.gcc.patches/343476 What happened with those?
There is also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51712 It would be great if that was eventually fixed in the new delay-folding world.
Noted. jeff
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |