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] |

*From*: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)*To*: iant at google dot com*Cc*: ebotcazou at adacore dot com, gcc-patches at gcc dot gnu dot org, mark at codesourcery dot com, matz at suse dot de, richard dot guenther at gmail dot com*Date*: Fri, 12 Oct 2007 07:47:07 EDT*Subject*: Re: [PATCH] Fix optimization regression in constant folder*References*: <200709171539.26653.ebotcazou@adacore.com> <200709301801.39718.ebotcazou@adacore.com> <m3r6kf3gyx.fsf@localhost.localdomain> <200710010127.59677.ebotcazou@adacore.com> <m3abr33dbp.fsf@localhost.localdomain> <10710010056.AA15609@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0710010325340.23011@wotan.suse.de> <10710010257.AA21585@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0710010454060.23011@wotan.suse.de> <10710010344.AA22633@vlsi1.ultra.nyu.edu> <470D0C50.4080506@codesourcery.com> <Pine.LNX.4.64.0710111658530.23011@wotan.suse.de> <10710111536.AA24058@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0710111756080.23011@wotan.suse.de> <10710111616.AA25194@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0710111828400.23011@wotan.suse.de> <10710111651.AA26098@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0710111853060.23011@wotan.suse.de> <m3r6k13728.fsf@localhost.localdomain> <Pine.LNX.4.64.0710112011530.23011@wotan.suse.de> <10710111850.AA27 912@vlsi1.ultra.nyu.edu> <Pine.LNX.4.64.0710112057570.2 <m3wsttymh6.fsf@localhost.localdomain>

> The flags aren't fixed in stone. In fact, I just introduced them > earlier this year. So all this tells me is that we need to change the > flags. Why? As I keep saying, we already HAVE a flag to denote sizetypes: we don't need another one but can just use THAT one. Why muck around with flags that are designed for an entirely different purpose, namely to characterize user-visible types. > Again, it's a big deal because at the moment most of the gcc > maintainers don't understand the semantics. After all this discussion > I still barely have a handle on what you want. You are talking in > vague generalities, and you are unable to give us any actual code. > It's no wonder we remain confused. It is indeed hard to characterize the semantics of sizetypes in anything other than a case-by-case manner, as this discussion has shown. But, as I said, "the code" is in stor-layout.c: that's where the vast majority of the sizetype operations are found. I think the C front end has almost none, the Ada front end has only a few (mostly related to zero-length arrays), and I don't know how many the C++ front-end has, but I doubt it's very many either. So if we need to understand what types of operations are being done and what those operations are entitled to assume, stor-layout is the place to look.

**References**:**Re: [PATCH] Fix optimization regression in constant folder***From:*Ian Lance Taylor

**Re: [PATCH] Fix optimization regression in constant folder***From:*Richard Kenner

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Richard Kenner

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Richard Kenner

**Re: [PATCH] Fix optimization regression in constant folder***From:*Mark Mitchell

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Richard Kenner

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Richard Kenner

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Richard Kenner

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Ian Lance Taylor

**Re: [PATCH] Fix optimization regression in constant folder***From:*Michael Matz

**Re: [PATCH] Fix optimization regression in constant folder***From:*Ian Lance Taylor

Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|

Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |