Yao Qi wrote on 06/09/2005 08:48:16:
> I am work on a floating points test according to IEEE754 and IEEE754
specifies
> that seven invalid arithmetic operations shall deliver a NaN unless they
are
> trapped:
> sqrt(Negative), 0*Infinity, 0.0/0.0, Infinity/Infinity,
REMAINDER(Anything,0.0),
> R
Richard Kenner wrote on 06/09/2005 00:27:51:
> I'm watching it deal with
>
> # small_1 = PHI <32(0), 1(1)>
>
> vrp_meet is called with [32, 32] and [1,1].
>
> It determines that the ranges don't intersect and then comes up with
> ~[0,0] since neither contain zero. But wouldn't [1,3
I am work on a floating points test according to IEEE754 and IEEE754 specifies
that seven invalid arithmetic operations shall deliver a NaN unless they are
trapped:
sqrt(Negative), 0*Infinity, 0.0/0.0, Infinity/Infinity, REMAINDER(Anything,0.0),
REMAINDER(Infinity, Anything), Infinity - Infinity.
[EMAIL PROTECTED] (Richard Kenner) writes:
> [Sorry for the missing line in my last message.]
>
> I'm watching it deal with
>
> # small_1 = PHI <32(0), 1(1)>
>
> vrp_meet is called with [32, 32] and [1,1].
>
> It determines that the ranges don't intersect and then comes up with
> ~[
I hope it's not bad etiquette to ping a PR but I would greatly
appreciate it if someone could take a quick look at PR 22207 which has
gone for several months with no replies.
The problem involves bogus "might be used uninitialized" warnings in STL
headers, but only at -O2 and above. This makes b
On Sep 5, 2005, at 6:39 PM, Richard Henderson wrote:
On Mon, Sep 05, 2005 at 02:27:54PM +0200, Andreas Krebbel wrote:
(insn 31 29 49 5 (set (mem/s/j:SI (plus:SI (reg/v/f:SI 47 [ env ])
(const_int 4 [0x4])) [0 .ex+0 S4 A32])
(mem/f:SI (plus:SI (plus:SI (reg:SI 55)
I am working on variable arguments on rs6000 backend and I have browsed
gcc/config/rs6000/rs6000.c for several times, I found there are
some functions relavtive to this issue, they are setup_incoming_varargs,
rs6000_build_builtin_va_list ,rs6000_va_start ,rs6000_gimplify_va_arg .
I
On Sep 5, 2005, at 6:39 PM, Richard Henderson wrote:
On Mon, Sep 05, 2005 at 02:27:54PM +0200, Andreas Krebbel wrote:
(insn 31 29 49 5 (set (mem/s/j:SI (plus:SI (reg/v/f:SI 47 [ env ])
(const_int 4 [0x4])) [0 .ex+0 S4 A32])
(mem/f:SI (plus:SI (plus:SI (reg:SI 55)
Thanks for your suggestion.
I think I need to port glibc. Because the new board is going to run
linux kernel. But I'm still not sure if glibc will support the new
target well. Thanks.
Eric
On Tue, Sep 06, 2005 at 09:48:18AM +0800, Eric Fisher wrote:
> hi,
>
> Would you tell me which I should select to port for the new target?
> The new target is like mips-elf. But I was told that glibc doesn't
> support mips-elf well. Is it right?
Glibc is a C library for (mostly) GNU/Linux target
Here's a fragment of the SSA dump for a shortened version of that
test.
D.860_8 = __gnat_malloc (20);
# D.861_10 = V_MUST_DEF ;
D.861 = (struct c34007p__designated *) D.860_8;
# VUSE ;
VIEW_CONVERT_EXPR(*D.861).b = 1;
# VUSE ;
VIEW_CONVERT_EXPR(*D.861).l = 3;
There last two s
hi,
Would you tell me which I should select to port for the new target?
The new target is like mips-elf. But I was told that glibc doesn't
support mips-elf well. Is it right?
Thanks for your help.
Eric
On Mon, Sep 05, 2005 at 02:27:54PM +0200, Andreas Krebbel wrote:
> (insn 31 29 49 5 (set (mem/s/j:SI (plus:SI (reg/v/f:SI 47 [ env ])
> (const_int 4 [0x4])) [0 .ex+0 S4 A32])
> (mem/f:SI (plus:SI (plus:SI (reg:SI 55)
> (reg:SI 56))
> (cons
Why doesn't it use fold-const.c:merge_ranges instead of having a subset
of that code?
Suppose lhs_vr is [64,64] and vr_result is ~[0,0]. It would seem
that the code near the end of this function will malfunction.
Shouldn't the test be that both lhs_vr *and* vr_result are VR_RANGE?
This is causing an ACATS failure in c45651a and possibly others.
On Monday 05 September 2005 23:26, Richard Kenner wrote:
> I'm watching it deal with
>
> # small_1 = PHI <32(0), 1(1)>
>
> vrp_meet is called with [32, 32] and [1,1].
>
> It determines that the ranges don't intersect and then comes up with
> result?
I would hope VR_VARYING...?
Gr.
Steven
[Sorry for the missing line in my last message.]
I'm watching it deal with
# small_1 = PHI <32(0), 1(1)>
vrp_meet is called with [32, 32] and [1,1].
It determines that the ranges don't intersect and then comes up with
~[0,0] since neither contain zero. But wouldn't [1,32] be a bett
I'm watching it deal with
# small_1 = PHI <32(0), 1(1)>
vrp_meet is called with [32, 32] and [1,1].
It determines that the ranges don't intersect and then comes up with
result?
in http://gcc.gnu.org/ml/gcc-patches/2005-08/msg01489.html
I've described a problem where regrename renamed a general
register creating an insn which does not satisfy the insn
predicate anymore.
I agree that regrename shouldn't make such replacements.
Constraints are important to drive reload, a
On Monday 05 September 2005 17:35, Peter S. Mazinger wrote:
> Hello!
>
> libssp subdir is present in cvs (checked on savannah) but cvs -q upd does
> not get it. Is it a cvs-server failure or something on my side?
cvs upd -d -P ?
Or better yet: contrib/gcc_update
Gr.
Steven
On Mon, 5 Sep 2005, Andrew Pinski wrote:
>
> On Sep 5, 2005, at 11:35 AM, Peter S. Mazinger wrote:
>
> > Hello!
> >
> > libssp subdir is present in cvs (checked on savannah) but cvs -q upd
> > does
> > not get it. Is it a cvs-server failure or something on my side?
>
> You want to update with
On Sep 5, 2005, at 11:35 AM, Peter S. Mazinger wrote:
Hello!
libssp subdir is present in cvs (checked on savannah) but cvs -q upd
does
not get it. Is it a cvs-server failure or something on my side?
You want to update with "cvs -q up -d -P", -d is required to get the new
directories.
-- P
Hello!
libssp subdir is present in cvs (checked on savannah) but cvs -q upd does
not get it. Is it a cvs-server failure or something on my side?
Thanks, Peter
--
Peter S. MazingerID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
On Sep 5, 2005, at 8:27 AM, Andreas Krebbel wrote:
Hello Richard,
s390 and s390x can't bootstrap with the following patch, because the
new assertion
introduced with the fixup_eh_region_note function is triggered.
Note this is recorded as PR 23711.
Thanks,
Andrew Pinski
Hi all,
In the end I modified TARGET_SCHED_ADJUST_COST to increase the cost of
anti-dependencies between a jump and another instruction, to prevent
them from being scheduled in the same cycle. This fix works well. It
still allows other independent instructions to be scheduled into the
same VL
Hello Richard,
s390 and s390x can't bootstrap with the following patch, because the new
assertion
introduced with the fixup_eh_region_note function is triggered.
http://gcc.gnu.org/ml/gcc-cvs/2005-08/msg01022.html
2005-08-31 Richard Henderson <[EMAIL PROTECTED]>
PR rtl-opt/23601
On Thu, 1 Sep 2005, Peter O'Gorman wrote:
> Another alternative would be to set RANLIB=: before configure if your
> system does not need to ranlib anything.
Thanks for the nice hint - this is what the FreeBSD Ports Collection
now uses for the lang/gcc34 to lang/gcc41 ports. ;-)
On Fri, 2 Sep 200
27 matches
Mail list logo
