Hi,
> > but you only take the hash of the argument of the phi node (i.e., the
> > ssa name), not the computations on that it is based
>
> Is this something like what you had in mind ?
>
> gen_hash (stmt)
> {
>
> if (stmt == NULL)
> return 0;
>
> use_operand_p use_p;
> ssa_op_
On Wed, Oct 15, 2008 at 8:37 AM, Zdenek Dvorak <[EMAIL PROTECTED]> wrote:
> Hi,
>
>> > but you only take the hash of the argument of the phi node (i.e., the
>> > ssa name), not the computations on that it is based
>>
>> Is this something like what you had in mind ?
>>
>> gen_hash (stmt)
>> {
>>
>>
Hi, I'm a guy working with gcc4.1.1 on itanium2. In my work, some
instrumentations are added by gcc. After instrumentation, all
specint2000 benchmarks except gzip can successfully run with
optimization flag -O3. There are some information list below:
1. Gzip can successfully run when compile with
Revital1 Eres wrote:
Hello,
I want to emit the following SPU insn:
emit_insn (gen_iorti3 (r77, tmp, GEN_INT(0)));
r77 is defined as 'fixed register' which is a register that the register
allocator can not use. (triggers by SPU option -mfixed-range)
r77 is used to pass information to some other
On Wed, Oct 15, 2008 at 11:17:18AM +0200, Revital1 Eres wrote:
>
> Hello,
>
> I want to emit the following SPU insn:
> emit_insn (gen_iorti3 (r77, tmp, GEN_INT(0)));
>
> r77 is defined as 'fixed register' which is a register that the register
> allocator can not use. (triggers by SPU option -mf
Hello,
I want to emit the following SPU insn:
emit_insn (gen_iorti3 (r77, tmp, GEN_INT(0)));
r77 is defined as 'fixed register' which is a register that the register
allocator can not use. (triggers by SPU option -mfixed-range)
r77 is used to pass information to some other routine at run-time (
Revital,
* Revital1 Eres <[EMAIL PROTECTED]> [2008-10-15 02:20]:
>
> r77 is defined as 'fixed register' which is a register that the register
> allocator can not use. (triggers by SPU option -mfixed-range)
> r77 is used to pass information to some other routine at run-time (the
> next instructio
The following problem is very common when dealing with iterators,
function objects and/or algorithms in C++. This is a simple test case:
#include
#include
#include
int main() {
using namespace std;
typedef istreambuf_iterator isbi;
string str(isbi(cin), isbi()); // Line 8
cou
Hello,
> > The problem is that r77 is not used in it's function after this
instruction
> > and thus DCE deletes it.
>
> Don't focus on DCE. That's not the problem; the fact that there's no
> visible dependence is the problem. Can you make the next instruction
> have a use for r77 explicitly (CAL
The following problem is very common when dealing with iterators,
function objects and/or algorithms in C++. This is a simple test case:
#include
#include
#include
int main() {
using namespace std;
typedef istreambuf_iterator isbi;
string str(isbi(cin), isbi()); // Line 8
cou
Date: Wed, 15 Oct 2008 15:15:45 -0400
To: [EMAIL PROTECTED]
From: James MacGregor <[EMAIL PROTECTED]>
Subject: We provide a web page with binaries of binutils/gcc/gdb you
might want add to http://gcc.gnu.org/install/binaries.html
Cc: "Craig Haller" <[EMAIL PROTECTED]>
Gentlemen:
Macraigor S
On Wed, Oct 15, 2008 at 09:54:36PM +0300, Lasse Kärkkäinen wrote:
> The following problem is very common when dealing with iterators,
> function objects and/or algorithms in C++.
Yes, I ran into this issue myself earlier this week. It's a more
general problem, striking whenever the arguments to a
Hi All,
I have a similar issue to what is reported here
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20143):
/Applications/avr/avr-src/gcc/unwind.h:59: error: unable to emulate 'DI'
As you clearly expressed by Paul, the underline issue that the target
only support data types up to 32-bits, while
Snapshot gcc-4.2-20081015 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20081015/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Dan and Richard,
Are either of you aware of the gcc.dg/vect/vect-67.c failure that is
occuring on some platforms? I see it on IA64 (Linux and HP-UX) but a
scan of the gcc-testresults mailing lists shows failures on x86_64 and
powerpc as well.
Looking into the failure, I see that it started (at l
Hello Everyone,
In GCC I found a MACRO called STRIP_NOPS and it is defined as the
following:
#define STRIP_NOPS(EXP) \
while ((TREE_CODE (EXP) == NOP_EXPR \
|| TREE_CODE (EXP) == CONVERT_EXPR\
On Thu, Oct 16, 2008 at 7:12 AM, Balaji V. Iyer <[EMAIL PROTECTED]> wrote:
> Hello Everyone,
>In GCC I found a MACRO called STRIP_NOPS and it is defined as the
> following:
>
> #define STRIP_NOPS(EXP) \
> while ((TREE_CODE (EXP) == NOP_EXPR
17 matches
Mail list logo
