2010/8/24 Basile Starynkevitch :
> Hello All
>
> Jeremie Salvucci and me Basile are working on improving gengtype. Our
> patch is still buggy [curious people might retrieve it from
> http://starynkevitch.net/Basile/gengtype-r163335-24august-2010.diff
I was meaning to take a look to get an idea wha
On Tue, 2010-08-24 at 15:19 -0700, Ian Lance Taylor wrote:
>
> > However, our patch also added some improvements to gengtype itself
>
> Improvements are desirable, but if it is all possible you should
> separate these improvements from your other work. It is very hard to
> review patches which c
Hello,
I have a problem about the definition of SHIFT_COUNT_TRUNCATED. MIPS
is a SHIFT_COUNT_TRUNCATED target, and has it defined as 1. While
loongson-specific vector insns are not SHIFT_COUNT_TRUNCATED. That
means that the macro depends on the machine mode. One simple
resolution may be,
#defin
Snapshot gcc-4.4-20100824 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20100824/
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
On 08/24/2010 07:38 PM, Basile Starynkevitch wrote:
> * what is the preferred way of obtaining a sequence of small patches?
> svn diff -x -p gives one big *.diff file! Should we split it by hand?
> Are there other tools producing a sequence of small patches?
http://savannah.nongnu.org/projects/qui
Basile Starynkevitch writes:
> * what is a sequence of related small patches? Is it an ordered set of
> patches to apply in succession? By what exact set of commands (assuming
> a GNU/Linux system). Does a latter patch in that sequence apply to the
> trunk, or to the trunk updated by previous pa
Possibly a note for:
http://gcc.gnu.org/install/specific.html
under OpenBSD.
or just for the mail archives:
Building a *slight* fork of 4.5.1 on OpenBSD/x86 4.7 I hit
gcc -c -g -O2 -static -DIN_GCC -W -Wall -Wwrite-strings \
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attr
Hello All
Jeremie Salvucci and me Basile are working on improving gengtype. Our
patch is still buggy [curious people might retrieve it from
http://starynkevitch.net/Basile/gengtype-r163335-24august-2010.diff but
I will remove that 267Kytes file of 9278 lines in a few days, and that
file is a *bugg
"Bingfeng Mei" writes:
> I came across an issue regarding named section and nobits. In
> the following example, I expected the c is placed is placed
> in a section named .smemdata and nobits is set for the section
> since "c" is initialized to zeros.
>
> int a = 0;
>
> int b = 2000 * 512;
> sta
"Paulo J. Matos" writes:
> In a rule like
> (set (match_operand 0 ...)
> (match_operand 1 ...))
>
> I sometimes have operand0 equal to operand1, as in
> rtx_equal_p(operand[0], operand[1]) == 1.
> This generates a move between the same location (same as a nop).
>
> Is there a reason for
Hello,
I came across an issue regarding named section and nobits. In
the following example, I expected the c is placed is placed
in a section named .smemdata and nobits is set for the section
since "c" is initialized to zeros.
int a = 0;
int b = 2000 * 512;
static int c[(200 * 512)] __attribute
Hello,
In a rule like
(set (match_operand 0 ...)
(match_operand 1 ...))
I sometimes have operand0 equal to operand1, as in
rtx_equal_p(operand[0], operand[1]) == 1.
This generates a move between the same location (same as a nop).
Is there a reason for getting this and is it up to me to
On Mon, Aug 23, 2010 at 6:43 PM, Ian Lance Taylor wrote:
>
> This also makes no sense. The operand predicate should test whether the
> value is acceptable. The constraints should tell the register allocator
> where the value should go. The paragraph you quoted is saying that the
> operand predi
13 matches
Mail list logo
