> 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 with documentation is, well,
> unappealing to me.
How can you fix bugs in Solaris' /bin/sh?
--
Eric Botca
On Fri, Apr 22, 2005 at 09:52:30PM +0200, Eric Botcazou wrote:
> > 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 with documentation is, well,
> > un
On Fri, 2005-04-22 at 15:56, Paul Schlie wrote:
> - Why are string literal character arrays not constructed and expanded as
> character array literals are?
They are constructed and expanded differently, because, obviously, they
are different things. I don't understand the point of this question
Current GCC CVS Mainline fails to bootstrap for me:
stage1/xgcc -Bstage1/ -B/opt/gcc/4.1-devel/x86_64-suse-linux-gnu/bin/ -c -g
-O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros
-Wold-style-definition -Werror -fno-c
Here are three build status reports for GCC 4.0.0.
#1: i686-pc-linux-gnu on Red Hat Enterprise version 3 (Xeon).
Languages: C, C++, Obj-C, Java.
Results:
http://gcc.gnu.org/ml/gcc-testresults/2005-04/msg01541.html
#2: x86_64-unknown-linux-gnu on Red Hat Enterprise version 3
(AMD O
Sebastian Biallas wrote:
But I noticed some smaller optimization issues on x86, and on of them is
a regression to gcc 3.3 so I'm reporting this here. Accept my apologies
if this is already known, but I think it's worth noting.
You can submit optimization regressions into our bugzilla bug database.
On Friday, April 22, 2005, at 12:52 PM, Eric Botcazou wrote:
How can you fix bugs in Solaris' /bin/sh?
See the re-exec logic in autoconf was it.
On Thu, Apr 21, 2005 at 06:10:19PM -0700, Bryan Richter wrote:
> I am working on porting GCC to the TI C54x.
Cool.
> months, similar to others who have attempted this project, but I am now
> in the process of setting up a repository on BerliOS so I can work with
> others.
Maybe not so cool, unle
Snapshot gcc-3.4-20050422 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/3.4-20050422/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 3.4 CVS branch
with the following options: -rgcc-ss-3_4-20050422
You'll find:
Hello,
If you will comple with gcc (version lower than 4) a program like this , on
Linux:
int main()
{
char* myString = "test";
(*myString)++;
}
You will get a segfault when running it.
On the other hand, if you will pass -fwriteable-strings at compilation ,
you will be able to r
On Fri, 2005-04-22 at 04:58, Paul Schlie wrote:
> Thanks. After going through the code, it's even further not clear why
> STRING_CST string literal data references treated differently than
> static const char array literal data references to begin with?
> Why is this necessary?
Why is what necessa
Joe Buck wrote:
> Maybe not so cool, unless you are careful. The problem is that if you
> don't keep track of who submitted what, or if you accept some critical
> code from someone who is either unwilling or unable to legally contribute
> their work to the FSF, it can never be accepted as part of
James E Wilson <[EMAIL PROTECTED]> writes:
> Greg McGary wrote:
> > I found that
> > emit_no_conflict_block() reordered insns gen'd by
> > expand_doubleword_shift() in a way that violated dependency between
> > compares and associated conditional-move insns that had the target
> > register as dest
> From: James E Wilson <[EMAIL PROTECTED]>
>> On Fri, 2005-04-22 at 04:58, Paul Schlie wrote:
>> Thanks. After going through the code, it's even further not clear why
>> STRING_CST string literal data references treated differently than
>> static const char array literal data references to begin wi
> Output from running srcdir/config.guess. Do not send that file itself, just
> the one-line output from running it.
i686-pc-linux-gnu
> The output of gcc -v for your newly installed gcc. This tells us which
> version of GCC you built and the options you passed to configure.
Using built-in s
I've bootstrap built GCC 4.0.0 on Fedora Core 3.
[EMAIL PROTECTED] ~]$ gcc -v
Using built-in specs.
Target: athlon-fedora-linux
Configured with: ../configure --prefix=/opt2/gcc4 --enable-shared
--enable-threads=posix --disable-checking
--with-system-zlib--enable-__cxa_atexit --disable-libunwind-ex
On Thu, 14 Apr 2005, Dale Johannesen wrote:
> On Apr 14, 2005, at 7:14 AM, Andrew Pinski wrote:
> >>Does this bug look familiar? 20629 is ICEing in the same spot, but
> >>it looks like theirs was reproducible after preprocessing. Is there
> >>any more information that I provide that would be hel
Hi there,
I successfully built gcc-4.0.0:
config.guess
i686-pc-linux-gnu
gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.0.0/configure
--prefix=/usr/local/test/gcc-4.0.0
--with-local-prefix=/usr/local/test/gcc-4.0.0 --enable-threads
--enable-languages=ada,c,c++,
Hello!
If I compile with
$ ~/usr/bin/gcc-4.0.0 -S Com_Code.cc -ffast-math -O2
the relevant generated code section is
#APP
fldln2; fxch; fyl2x
#NO_APP
fmulp %st, %st(2)
fxch%st(1)
#APP
fsqrt
#NO_APP
fld %st(1)
#APP
fsin
#NO_APP
fxch
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
On Fri, Apr 22, 2005 at 09:59:18AM +0200, Adrian von Bidder wrote:
> 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 la
On Fri, Apr 22, 2005 at 12:32:23AM -0400, Andrew Pinski wrote:
>
> On Apr 22, 2005, at 12:27 AM, Eric Lemings wrote:
>
> >FYI,
> >
> >Downloaded gcc-core-4.0.0.tar.bz and gcc-g++-4.0.0.tar.bz2.
> >Uncompressed both and did a configure followed by a make.
> >Got the following error from make:
>
>
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 gfortran itself - there
Hello,
I casually found a bug in the current released GCC 4.0.0. However, I
have located the wrong code, and it's very easy to be fixed, so it's not
necessary to still submit a bug report. See the following artificial
C++ code:
int *x;
void f()
{
do
Hi,
finally, gcc 4.0.0 is released and it builds on IRIX 6.3
(as opposed to my numerous failing tries of gcc 3.x.y).
lucy 70% ./gcc-4.0.0/config.guess
mips-sgi-irix6.3
lucy 71% /usr/gcc-4.0/bin/gcc -v
Using built-in specs.
Target: mips-sgi-irix6.3
Configured with: /usr/people/eblachut/dev/gcc-4.
On Sat, Apr 23, 2005 at 09:07:23AM +0200, Andreas Jaeger wrote:
> Current GCC CVS Mainline fails to bootstrap for me:
>
Odd, my x86_64 works just fine. Send me a .i file?
Thanks. Diego.
On Saturday, April 23, 2005, at 12:35 AM, sting sting wrote:
If you will comple with gcc
This is the wrong list, please use gcc-help in the future.
What are the disadvantages of using -fwritable-strings
Acceptance of non-portable code.
and why was it removed ?
The 1980s are over. People didn't wa
> From: Zack Weinberg <[EMAIL PROTECTED]>
>> 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
On Apr 23, 2005, at 6:35 AM, ~{Dt>Clb~} wrote:
Hello,
I casually found a bug in the current released GCC 4.0.0. However, I
have located the wrong code, and it's very easy to be fixed, so it's
not
necessary to still submit a bug report. See the following artificial
C++ code:
int *x;
> From: Paul Schlie <[EMAIL PROTECTED]>
> ...
> (with respect to: -Wwrite-strings, I would have thought that the option,
> although presently depreciated and disabled by default, would only have
> enabled writes to string literal references be specified at the language
> front-end level, but not
The description of tcc_statement in tree.h says "A statement
expression, which have side effects but usually no interesting value."
There are a number of entries in cp/cp-tree.def which are marked as
tcc_expression, although they seem to me to be better described as
tcc_statement, to wit:
IF_STMT
James E Wilson wrote:
Ling-hua Tseng wrote:
It's obvious that `movil' and `movim' are only access the partial
16-bit of the 32-bit register. How can I use RTL expression to
represent the operations?
As you noticed, within a register, subreg can only be used for low
parts. You can't ask for the h
Ian Lance Taylor wrote:
The description of tcc_statement in tree.h says "A statement
expression, which have side effects but usually no interesting value."
There are a number of entries in cp/cp-tree.def which are marked as
tcc_expression, although they seem to me to be better described as
tcc_stat
I configured/made/installed gcc 4.0.0 partially on a Solaris host. I
could not build with C++ support, because ld (GNU ld, that is) choked
(dumped core, signal 11, segmentation violation) on abi_check (see
below).
When using the Sun-supplied as and ld, ld chokes on alignment errors
during bootstra
On Sat, 23 Apr 2005, Jeroen Scheerder wrote:
> Note that builds on Solaris 10 on AMD Opteron (on a Sun Fire V20z) failed
> miserably. With the Sun-supplied as and ld, bootstraps chokes on syntax
> errors in assembly files; with GNU as and ld, bootstrap chockes on
> invalid instructions (64-bit AM
After some discussion, how to create transparent access to different
memory transparently, I propose the following solution:
We change the GCC core to store the type of each memory expression
in the MEM rtx. Backends can use this type information to create a diffent RTL
or output a different assem
Ian Lance Taylor writes:
| The description of tcc_statement in tree.h says "A statement
| expression, which have side effects but usually no interesting value."
|
| There are a number of entries in cp/cp-tree.def which are marked as
| tcc_expression, although they seem to me to be better describ
Could anyone help me understand what is the gcc
strategy to prepare the stack frame?
For the following function,
void function(int a, int b, int c)
{
char buffer1[5];
char buffer2[10];
int *ret;
ret = &buffer1[0]+28;
printf("0x%x=return address, *ret);
}
I compiled with gcc -O0 -S
> Martin Koegler wrote:
> ...
> Before I start experimenting with this, I want other people opinions,
> how acceptable this proposal will before GCC mainline or if it can be
> improved.
- sound's good, and a natural generalization of current mem ref attributes.
(However ideally, function paramete
On Sat, Apr 23, 2005 at 07:18:22PM +0200, Martin Koegler wrote:
> For implementing the type attributes, I propose:
> Add the field "tree type;" to "struct mem_attrs". This field holds the type,
> if present,
> or 0, if no type information is available.
>
> To access it, I propose:
> #define MEM_T
> From: Paul Schlie <[EMAIL PROTECTED]>
>> Martin Koegler wrote:
>> ...
>> Before I start experimenting with this, I want other people opinions,
>> how acceptable this proposal will before GCC mainline or if it can be
>> improved.
>
> - sound's good, and a natural generalization of current mem ref
Joseph S. Myers:
> On Sat, 23 Apr 2005, Jeroen Scheerder wrote:
>
> > Note that builds on Solaris 10 on AMD Opteron (on a Sun Fire V20z) failed
> > miserably. With the Sun-supplied as and ld, bootstraps chokes on syntax
> > errors in assembly files; with GNU as and ld, bootstrap chockes on
> > i
Hi,
I have been adding some profiling stuff onto the RTL. I get the following
error in reload phase. Can someone tell me how to fix this? I use 8th
April 2005
check out from CVS.
./mul_mdmd_md.c: In function âmul_mdmd_md_l1_arb_allâ:
./mul_mdmd_md.c:343: error: unable to find a register to spi
On Sunday 24 April 2005 00:22, Rajkishore Barik wrote:
> Hi,
>
> I have been adding some profiling stuff onto the RTL. I get the following
> error in reload phase. Can someone tell me how to fix this? I use 8th
> April 2005 check out from CVS.
Hmm, let me rephrase your question:
"I did some GCC ha
On Wed, 6 Apr 2005, Joseph S. Myers wrote:
> (If test results for a port are so bad that
> though sent to gcc-testresults they exceed the message size limit, and
> this remains the case for a prolonged period such as ever since 4.0
> branched, that also indicates lack of active maintenance.)
No, i
On Sat, 23 Apr 2005, Hans-Peter Nilsson wrote:
> On Wed, 6 Apr 2005, Joseph S. Myers wrote:
> > (If test results for a port are so bad that
> > though sent to gcc-testresults they exceed the message size limit, and
> > this remains the case for a prolonged period such as ever since 4.0
> > branched
Snapshot gcc-4.0-20050423 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20050423/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.0 CVS branch
with the following options: -rgcc-ss-4_0-20050423
You'll
On Apr 23, 2005, at 7:40 PM, Hans-Peter Nilsson wrote:
On Sat, 23 Apr 2005, Hans-Peter Nilsson wrote:
On Wed, 6 Apr 2005, Joseph S. Myers wrote:
(If test results for a port are so bad that
though sent to gcc-testresults they exceed the message size limit,
and
this remains the case for a prolonged
I am writing a gui app in another language that needs the gcc compiler
embedded into it (or at least along for the ride), in case the user
doesn't have it on their system.
What's the smallest size I can squeeze gcc down to and how would I go
about compiling it in such a way?
I'm on an OS X box
Running the libstdc++ testsuite on NetBSD/sparc or NetBSD/sparc64
results in most tests failing like:
:1: fatal error: had to relocate PCH
compilation terminated.
compiler exited with status 1
This is due to a misassumption in ggc-common.c:654
(mmap_gt_pch_use_address):
This version assumes that
> Hmm, let me rephrase your question:
> "I did some GCC hacking that I'm not showing, and it doesn't work,
> please help me fix it."
This is not what I meant. I meant if similar problem has been reported by
anyone else before. In any case. This is the piece of code that I add
after every integer
Bryan Richter wrote:
> Joe Buck wrote:
> >
> >
> > Please read
> >
> > http://gcc.gnu.org/contribute.html
>
> Right- I've read this and I'm aware of the situation. I am prepared to 'keep
> my
> ducks in a row'. :)
After mulling it over for a day, I now realize that developing it separately is
On Apr 23, 2005, at 5:42 PM, Matt Thomas wrote:
Running the libstdc++ testsuite on NetBSD/sparc or NetBSD/sparc64
results in most tests failing like:
:1: fatal error: had to relocate PCH
compilation terminated.
compiler exited with status 1
This is due to a misassumption in ggc-common.c:654
(mmap_g
When -fprofile-arcs is used, the directory of profile data is fixed
to the build directory. If I want to run the binary on a different
machine, I have to create the same directory, which may not be very
easy. Is this intentional? Can we have have an option to specify the
different dirctory or to us
Hi,
Any bechmarks which are dynamic storage alloca intensive? Or
call malloc like func a lot?
Thanks,
Zhenyu
Matt Thomas <[EMAIL PROTECTED]> writes:
> Running the libstdc++ testsuite on NetBSD/sparc or NetBSD/sparc64
> results in most tests failing like:
>
> :1: fatal error: had to relocate PCH
> compilation terminated.
> compiler exited with status 1
>
> This is due to a misassumption in ggc-common.c:
Rajkishore Barik <[EMAIL PROTECTED]> writes:
> > Hmm, let me rephrase your question:
> > "I did some GCC hacking that I'm not showing, and it doesn't work,
> > please help me fix it."
>
> This is not what I meant. I meant if similar problem has been reported by
> anyone else before.
Everybody w
Successful build:
$ which as; as --version
/phil/sw/sunos/sparc/bin/as
GNU assembler 2.15.97 20050420
Copyright 2005 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no
i am now writing a frontend in gcc,
but i don`t understand the rule to write the makefile.in, config-lang.in
59 matches
Mail list logo
