Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Sandiford
Kenneth Zadeck writes: > However, i would also say that it would be nice if were actually done > right. There are (as far as i know) actually 3 ways handling shift > amounts that have been used in the past: > > (1) mask the shift amount by (bitsize - 1). This is the most popular > and is wh

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Kenneth Zadeck
On 11/04/2013 04:12 AM, Richard Biener wrote: On Fri, 1 Nov 2013, Richard Sandiford wrote: I'm building one target for each supported CPU and comparing the wide-int assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding output from the merge point. This patch removes all th

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Biener
On Mon, 4 Nov 2013, Richard Sandiford wrote: > Richard Biener writes: > > On Mon, 4 Nov 2013, Richard Biener wrote: > > > >> On Fri, 1 Nov 2013, Richard Sandiford wrote: > >> > >> > I'm building one target for each supported CPU and comparing the wide-int > >> > assembly output of gcc.c-torture,

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Biener
On Mon, 4 Nov 2013, Richard Sandiford wrote: > Richard Biener writes: > > On Fri, 1 Nov 2013, Richard Sandiford wrote: > >> I'm building one target for each supported CPU and comparing the wide-int > >> assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding > >> output from th

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Sandiford
Richard Biener writes: > On Mon, 4 Nov 2013, Richard Biener wrote: > >> On Fri, 1 Nov 2013, Richard Sandiford wrote: >> >> > I'm building one target for each supported CPU and comparing the wide-int >> > assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding >> > output from t

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Sandiford
Richard Biener writes: > On Fri, 1 Nov 2013, Richard Sandiford wrote: >> I'm building one target for each supported CPU and comparing the wide-int >> assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding >> output from the merge point. This patch removes all the differences I

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Biener
On Mon, 4 Nov 2013, Richard Biener wrote: > On Fri, 1 Nov 2013, Richard Sandiford wrote: > > > I'm building one target for each supported CPU and comparing the wide-int > > assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding > > output from the merge point. This patch remo

Re: [wide-int] Avoid some changes in output code

2013-11-04 Thread Richard Biener
On Fri, 1 Nov 2013, Richard Sandiford wrote: > I'm building one target for each supported CPU and comparing the wide-int > assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding > output from the merge point. This patch removes all the differences I saw > for alpha-linux-gnu i

Re: [wide-int] Avoid some changes in output code

2013-11-01 Thread Kenneth Zadeck
On 11/01/2013 09:31 AM, Richard Sandiford wrote: Kenneth Zadeck writes: On 11/01/2013 04:46 AM, Richard Sandiford wrote: I'm building one target for each supported CPU and comparing the wide-int assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding output from the merge po

Re: [wide-int] Avoid some changes in output code

2013-11-01 Thread Richard Sandiford
Kenneth Zadeck writes: > On 11/01/2013 04:46 AM, Richard Sandiford wrote: >> I'm building one target for each supported CPU and comparing the wide-int >> assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding >> output from the merge point. This patch removes all the differenc

Re: [wide-int] Avoid some changes in output code

2013-11-01 Thread Kenneth Zadeck
On 11/01/2013 04:46 AM, Richard Sandiford wrote: I'm building one target for each supported CPU and comparing the wide-int assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding output from the merge point. This patch removes all the differences I saw for alpha-linux-gnu in g

[wide-int] Avoid some changes in output code

2013-11-01 Thread Richard Sandiford
I'm building one target for each supported CPU and comparing the wide-int assembly output of gcc.c-torture, gcc.dg and g++.dg with the corresponding output from the merge point. This patch removes all the differences I saw for alpha-linux-gnu in gcc.c-torture. Hunk 1: Preserve the current trunk b