Mike Stump <[EMAIL PROTECTED]> writes:
> Not being able to build in the source directory is a bug.
> Having to set CONFIG_SHELL is a bug.
> Having to install a newer cctools is a bug.
Patches are welcome.
zw
Toon Moene wrote:
Mark Mitchell wrote:
The GCC 4.0 branch is now open for regression fixes only, under the
usual release branch rules.
I presume this means that we (The Fortran Illuminati) can fix any bug in
the gfortran frontend, as we don't have any regressions yet (at least
not against gfort
Hi,
I'm interested in gcc 4.0.0 because I believe it's supposed to generate
the fsincos instruction on x86 when appropriate.
I have the following code sample which I use to generate two random
Gaussian numbers, for which I think fsincos should probably be generated
by the compiler,
typedef dou
On Fri, Apr 22, 2005 at 10:26:25AM -0400, Kazu Hirata wrote:
> Hi Rainer and Steve,
>
> > | 4.1.0 20050419 (experimental) (i386-pc-solaris2.10) GCC error: |
> > | in set_value_range, at tree-vrp.c:124|
> > | Error detected at sem_intr.adb:437:1
James E Wilson wrote:
> You were never very clear about what was wrong with gen_highpart and
> gen_lowpart with respect to subregs. rtl examples are always helpful,
> e.g. showing RTL input and RTL output and pointing out what is wrong.
> gen_lowpart already has support for subreg input and presu
On Thursday, April 21, 2005, at 08:57 PM, Andrew Pinski wrote:
Does anyone read the installation instructions?
No.
Not being able to build in the source directory is a bug.
Having to set CONFIG_SHELL is a bug.
Having to install a newer cctools is a bug.
Bugs should be fixed. Papering over them wi
I built
i686-pc-linux-gnu native
i686-pc-linux-gnu X mips64-unknown-elf
sparc-sun-solaris2.8 native
just fine, but have a problem with:
sparc-sun-solaris2.8 X mips64-unknown-elf
Specifically the xgcc was linked, but won't run:
/gcc/xgcc -dumpspecs
James E Wilson <[EMAIL PROTECTED]> writes:
>> unnecessary, and error prone (as evidenced by string literal memory
>> references not being properly identified as READONLY, although their
>> equivalent array representations are treated properly for example?)
>
> If true, that sounds like a bug
James E Wilson <[EMAIL PROTECTED]> wrote:
Andrew Pinski wrote:
Does anyone read the installation instructions?
Yes, but not everyone. And even people that read the docs can miss the
info if they can't figure out which part of the docs they are supposed
to be looking at.
If you don't want people
Hi Rainer and Steve,
> | 4.1.0 20050419 (experimental) (i386-pc-solaris2.10) GCC error: |
> | in set_value_range, at tree-vrp.c:124|
> | Error detected at sem_intr.adb:437:1 |
There seem to be several ways to get to
Original Message
>From: Bingguang Peng
>Sent: 22 April 2005 13:19
> i want to join
http://gcc.gnu.org/lists.html
cheers,
DaveK
--
Can't think of a witty .sigline today
i want to join
> From: James E Wilson <[EMAIL PROTECTED]>
>> - One of the things that's been eluding me, is that I can't seem to find
>> where literal string constant mem references aren't being properly
>> declared and/or preserved as READONLY/unchanging references, resulting
>> in MEM_READONLY_P failing t
On Apr 22, 2005, at 6:25 AM, Andrew Haley wrote:
GCC regression checker writes:
With your recent patch, GCC HEAD has some regression test failures,
which used to pass. There are 0 new failures, and 75
failures that existed before and after that patch; 0 failures
have been fixed.
The old failures,
Per Bothner writes:
> Andrew Haley wrote:
> > However, these fields are real, and they are used, but we shouldn't
> > output any debug info for them.
>
> Does Dwarf support "computed field offsets"? (This might be needed
> for Ada, to.) If so, the Right Thing might be to emit DIEs so gdb
GCC regression checker writes:
> With your recent patch, GCC HEAD has some regression test failures,
> which used to pass. There are 0 new failures, and 75
> failures that existed before and after that patch; 0 failures
> have been fixed.
>
> The old failures, which were not fixed or intro
Original Message
>From: Zhaohui Zhou
>Sent: 22 April 2005 03:21
> Hi,
>
> I am wondering where I can find instructions on how to install GCC on
> my Windows XP computer. Thanks.
>
> Regards,
> Zhaohui Zhou
Your best bet is to install either cygwin (http://cygwin.com), which is a
full
Steve Kargl <[EMAIL PROTECTED]> writes:
> kargl[266] gfc41 -c cher2k.f
> kargl[267] gfc41 -c -O cher2k.f
> kargl[268] gfc41 -c -O2 cher2k.f
> cher2k.f: In function 'cher2k':
> cher2k.f:1: internal compiler error: in set_value_range, at tree-vrp.c:124
> Please submit a full bug report,
> with prepr
Hi,
Please forgive this remark - especially if it has been discussed before (I
don't follow this list.)
I think that Mark's key (0xB75C61B8) might not have been the best choice to
sign the gcc release because it lacks connections to the majority of the
OpenPGP web of trust, being signed only b
Andrew Pinski wrote:
Does anyone read the installation instructions?
Yes, but not everyone. And even people that read the docs can miss the
info if they can't figure out which part of the docs they are supposed
to be looking at.
If you don't want people sending bug reports like this, then you i
GCC 4.0.0 has been released.
This release is a major release, containing (among many other features)
new optimization infrastructure that enables GCC to perform more
high-level optimizations that has been possible in the past. A more
complete list of changes is at:
http://gcc.gnu.org/gcc-4.0/c
The GCC 4.0 branch is now open for regression fixes only, under the
usual release branch rules.
--
Mark Mitchell
CodeSourcery, LLC
[EMAIL PROTECTED]
(916) 791-8304
Martin Koegler wrote:
arg 1 >>
So, how to change this function? As a MEM_EXPR may only be a DECL or a
COMPONENT_REF,
storing a indriect_ref of a plus_expr is also not valid. This is, why I had to
change
the other functions.
There is a var_decl here inside the indirect_ref. Will using
23 matches
Mail list logo
