2011/12/13 Miles Bader :
> Jonathan Wakely writes:
> How about "...; suggest adding the using keyword"?
That sounds like the compiler is suggesting that the user suggests
doing that!
>>>
>>> It is similar to "suggest parentheses ...".
>>
>> Good point, that's not correct English
Hi,
I am finding slightly confusing the difference between
outgoing_args_size and pretend_args_size.
I think I understand pretend_args_size, at least on the specific case of
my port. The first two words of arguments go into two register the
remaining goes into the stack. However, if the firs
Hi guys,
While looking at Spec2006/401.bzip2 I found such a loop:
for (i = 1; i <= alphaSize; i++) {
j = weight[i] >> 8;
j = 1 + (j / 2);
weight[i] = j << 8;
}
Which is not vectorizeble (using Intel's AVX2) because division by two
is not recognized as rshift:
5: ==> exa
On Tue, 13 Dec 2011, Kirill Yukhin wrote:
> Hi guys,
> While looking at Spec2006/401.bzip2 I found such a loop:
> for (i = 1; i <= alphaSize; i++) {
> j = weight[i] >> 8;
> j = 1 + (j / 2);
> weight[i] = j << 8;
> }
>
> Which is not vectorizeble (using Intel's AVX2) beca
On Tue, Dec 13, 2011 at 02:07:11PM +0100, Richard Guenther wrote:
> > Hi guys,
> > While looking at Spec2006/401.bzip2 I found such a loop:
> > for (i = 1; i <= alphaSize; i++) {
> > j = weight[i] >> 8;
> > j = 1 + (j / 2);
> > weight[i] = j << 8;
> > }
It would be helpfu
The full case attached.
Jakub, you are right, we have to convert signed ints into something a
bit more tricky.
BTW, here is output for that cases from Intel compiler:
vpxor %ymm1, %ymm1, %ymm1 #184.23
vmovdqu .L_2il0floatpacket.12(%rip), %ymm0
On Tue, Dec 13, 2011 at 05:42:16PM +0400, Kirill Yukhin wrote:
> The full case attached.
>
> Jakub, you are right, we have to convert signed ints into something a
> bit more tricky.
> BTW, here is output for that cases from Intel compiler:
Ah, so that matches to do j / 2 in the pattern recognizer
Great!
Thanks, K
>
> Let me hack up a quick pattern recognizer for this...
>
> Jakub
"Paulo J. Matos" writes:
> I am finding slightly confusing the difference between
> outgoing_args_size and pretend_args_size.
>
> I think I understand pretend_args_size, at least on the specific case
> of my port. The first two words of arguments go into two register the
> remaining goes into the
On 13/12/11 14:47, Ian Lance Taylor wrote:
outgoing_args_size is the number of bytes required by called functions.
In your question above, the answer is no; x is an incoming argument. If
you write
extern foo(int);
void bar(void) { foo (1); }
then the outgoing_args_size of bar is sizeof(int), b
Are there plans to expand the number of targets for go in gcc 4.7?
In particular, PR46986 has had a proposed set of changes...
http://gcc.gnu.org/bugzilla/attachment.cgi?id=25196&action=diff
which should provide a starting point to identify the changes required
for go support on darwin.
Hi,
From an RTEMS perspective, the head has multiple regressions from the
4.6 branch. avr, bfin, lm32 and m68k have regressions such that they are
incapable of compiling a complete tool chain. This means they fail to
compile gcc, newlib, or RTEMS. These are the PRs for those regressions.
a
On 12/13/2011 01:35 PM, Jack Howarth wrote:
Are there plans to expand the number of targets for go in gcc 4.7?
In particular, PR46986 has had a proposed set of changes...
http://gcc.gnu.org/bugzilla/attachment.cgi?id=25196&action=diff
which should provide a starting point to identify the ch
Jack Howarth writes:
>Are there plans to expand the number of targets for go in gcc 4.7?
I would like to but I am also really swamped. I'm knocking down issues
as fast as I can.
My primary goal for gcc 4.7 is to include complete support for the
upcoming Go 1 standard release on GNU/Linux.
On 12/13/2011 2:16 PM, Ian Lance Taylor wrote:
Jack Howarth writes:
Are there plans to expand the number of targets for go in gcc 4.7?
I would like to but I am also really swamped. I'm knocking down issues
as fast as I can.
My primary goal for gcc 4.7 is to include complete support for
Joel Sherrill writes:
> Where should that discussion occur?
Here and/or gofrontend-...@googlegroups.com.
Sorry I have not replied to your earlier message, I will do so now.
Ian
Snapshot gcc-4.4-20111213 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20111213/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
I'm interested in your site. I just added your link http://gcc.gnu.org in my
website: http://hotelfrance24.com/Rome-site-list50/
Please add my link:
Title: Clock widget
URL: http://time-24.org/en/widgets/
html code: http://time-24.org/en/widgets/";>Clock widget
Best regards.
Hi,
I'll sponsor Oleg Endo as a new write after approval maintainer.
He has written several good patches for SH targets and has filed
good PRs. He is working on the issues which will require larger
patches and being write after approval looks to be helpful.
His paper work with FSF has done. OK?
2011/12/13 Joel Sherrill :
> Hi,
>
> From an RTEMS perspective, the head has multiple regressions from the 4.6
> branch. avr, bfin, lm32 and m68k have regressions such that they are
> incapable of compiling a complete tool chain. This means they fail to
> compile gcc, newlib, or RTEMS. These are th
20 matches
Mail list logo
