On Mon, Jan 08, 2007 at 08:09:59PM -0800, Andrew Pinski wrote:
> On Mon, 2007-01-08 at 18:25 -0800, H. J. Lu wrote:
> > I am enclosing a patch to implement a new linker swicth,
> > --dynamic-list-data. It is -Bsymbolic for function symbols only.
> > I tried it with C, C++, Java and Fortran on Linux
On Mon, 2007-01-08 at 18:25 -0800, H. J. Lu wrote:
> I am enclosing a patch to implement a new linker swicth,
> --dynamic-list-data. It is -Bsymbolic for function symbols only.
> I tried it with C, C++, Java and Fortran on Linux/ia32, Linux/x86-64
> and Linux/ia64. There are only a few regressions.
Howdy,
The build succeeded.
Thanks for the help.
George...
--- Jan Hubicka <[EMAIL PROTECTED]> wrote:
> > >
> > > > >`/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu/gcc'
> > > > >make[2]: *** [all-stage2-gcc] Error 2
> > > > >make[2]: Leaving directory
> > > > >`/rb.exphome/tools/gcc/obj-i686-p
I am enclosing a patch to implement a new linker swicth,
--dynamic-list-data. It is -Bsymbolic for function symbols only.
I tried it with C, C++, Java and Fortran on Linux/ia32, Linux/x86-64
and Linux/ia64. There are only a few regressions. The function calls
within the new resulting DSOs will bind
--- Jan Hubicka <[EMAIL PROTECTED]> wrote:
> > >
> > > > >`/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu/gcc'
> > > > >make[2]: *** [all-stage2-gcc] Error 2
> > > > >make[2]: Leaving directory
> > > > >`/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu'
> > > > >make[1]: *** [stage2-bubble] Error 2
> >
Snapshot gcc-4.1-20070108 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20070108/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.1 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
> I am pleased to announce that the GCC Steering Committee has
> appointed Jan Hubicka and Uros Bizjak as co-maintainers of the i386 port.
>
> Please join me in congratulating Jan and Uros on their new role.
> Jan and Uros, please update your listings in the MAINTAINERS file.
Thank yo
> >
> > > >`/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu/gcc'
> > > >make[2]: *** [all-stage2-gcc] Error 2
> > > >make[2]: Leaving directory `/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu'
> > > >make[1]: *** [stage2-bubble] Error 2
> > > >make[1]: Leaving directory `/rb.exphome/tools/gcc/obj-i686-pc
>
> > >`/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu/gcc'
> > >make[2]: *** [all-stage2-gcc] Error 2
> > >make[2]: Leaving directory `/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu'
> > >make[1]: *** [stage2-bubble] Error 2
> > >make[1]: Leaving directory `/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu'
> >`/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu/gcc'
> >make[2]: *** [all-stage2-gcc] Error 2
> >make[2]: Leaving directory `/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu'
> >make[1]: *** [stage2-bubble] Error 2
> >make[1]: Leaving directory `/rb.exphome/tools/gcc/obj-i686-pc-linux-gnu'
> >make: ***
Alexander Grobman wrote:
/tmp/ccvk5vjH.s:38: Error: operand must be absolute in
range 1..32, not 53
Some of the embedded target ports won't work if compiled on 64-bit
hosts. mcore-elf seems to be one of them. This problem sometimes shows
up as a gcc error and sometimes shows up as a binutil
Hello Nick,
Thanks for your support.
this is the error message I'm getting:
"
...
make[4]: Leaving directory
`/proj/tec/alpeca_lite/users/alexgr/gcc/objdir1/gcc'
/proj/tec/alpeca_lite/users/alexgr/gcc/objdir1/./gcc/xgcc
-B/proj/tec/alpeca_lite/users/alexgr/gcc/objdir1/./gcc/
-B/usr/local/mcore-el
On 1/8/07, George R Goffe <[EMAIL PROTECTED]> wrote:
/tools/gcc/obj-i686-pc-linux-gnu/./prev-gcc/xgcc
-B/tools/gcc/obj-i686-pc-linux-gnu/./prev-gcc/
-B/usr/lsd/Linux/x86_64-unknown-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-
/tools/gcc/obj-i686-pc-linux-gnu/./prev-gcc/xgcc
-B/tools/gcc/obj-i686-pc-linux-gnu/./prev-gcc/
-B/usr/lsd/Linux/x86_64-unknown-linux-gnu/bin/ -c -g -O2 -DIN_GCC -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long
-Wno-variadic-macros -Wno-overlength-stri
Richard Kenner wrote:
> (3) How many programs are known to rely on wrap semantics? For each:
> (a) How hard was it to determine there was a problem with that
> assumption?
A piece of data for GNU clisp and cln:
- For clisp, it was easy to find out and fix all problems, because the
I am pleased to announce that the GCC Steering Committee has
appointed Jan Hubicka and Uros Bizjak as co-maintainers of the i386 port.
Please join me in congratulating Jan and Uros on their new role.
Jan and Uros, please update your listings in the MAINTAINERS file.
Happy hacking!
This is only a test on Immobilien Hamburg. So please ignore.
http://www.hamburgimmobilie.de
___
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02
It seems I managed to mess up the patch applied to revision 120558.
The problem is that somehow all testcases have been added three times.
I cannot imagine how such thing happenned.
You probably used "patch" which, instead of warning if a patch creates a
file that is already there, happily puts
Dear all,
It seems I managed to mess up the patch applied to revision 120558.
The problem is that somehow all testcases have been added three times.
I cannot imagine how such thing happenned.
Anyway, I will fix it today as soon as I put my hands in my laptop. Is
it better to revert and re-apply
> Even if you fix that, gcc will only vectorize if you pass the
> -ftree-vectorize option. And it will only vectorize code in loops.
Supporting straight-line code vectorization is in the works, but at first
we'll look for such opportunities only in loops (i.e. exploit
vector-parallelism within an
20 matches
Mail list logo
