Porting PXE-GCC tool chain from GCC 3.2 to GCC 3.4.6
Hello Everyone!! I am trying to port GCC-PXE tool chain from GCC 3.2 to GCC 3.4.6. While building the PXE-GCCCross Compiler i am getting the following errors: ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c: In function `pxe_mark_machine_status': ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c:1673: warning: implicit declaration of function `ggc_mark_rtx' ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c: In function `pxe_init_expanders': ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c:1684: warning: assignment from incompatible pointer type ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c:1685: `mark_machine_status' undeclared (first use in this function) ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c:1685: (Each undeclared identifier is reported only once ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c:1685: for each function it appears in.) ../../../gcc-3.4.6/gcc-3.4.6/gcc/config/pxe/pxe.c:1686: `free_machine_status' undeclared (first use in this function) make[1]: *** [pxe.o] Error 1 make[1]: Leaving directory `/home/rohit/PXE-Migration/buildpxe3.4/gcc/gcc' make: *** [all-gcc] Error 2 - can any one tell me how is that variables mark_machine_status , free_machine_status and the ggc_mark_* macros are compensated or implemented in the newer version of GCC 3.4.6 Anticipating a quick response. Thanks and Regards, Rohit
code instrumentation in the tree structure
Hi everyone
I don't know if this is a development-list issue but I thought I'd try.
I'm writing a code instrumentation tool using the GEM
plugin-system (http://www.ecsl.cs.sunysb.edu/gem/) as a part of my
thesis project. I got it working in gcc-3.4 with a little help from the
GEM maintainer but I have realized I need to move to gcc-4 to get access
to the control-flow manipulation tools. Now my problem is that my code
which inserted function call statements does not work under the gcc-4
environment. the EXPR_STMT-symbol is gone for example. which makes the line
t_new_stmt = build_nt(EXPR_STMT, t_call);
cause compilation errors. Now, has the notion of statements been removed
in gcc-4, and in that case what has replaced it? I am quite confused at
the moment so if something doesn't make sense I'd be very happy with any
kind of explanation that makes me understand again. The following piece
of code is what I'm working with at the moment. It compiles but doesn't
really cause anything to happen when run.
void ci_insert_call(tree t_func, const char* func_name, tree args) {
tree t_func_decl;
tree t_body;
tree t_first_stmt;
tree t_call;
tree t_new_stmt;
t_body=DECL_SAVED_TREE(t_func); // COMPOUND_STMT
/* t_first_stmt = COMPOUND_BODY(t_body); */
gem_find_symtab(&t_func_decl, func_name);
t_call=build_function_call(t_func_decl, args);
t_new_stmt = build_nt(CALL_EXPR, t_call);
/* TREE_CHAIN(t_new_stmt)=TREE_CHAIN(t_first_stmt); */
/* TREE_CHAIN(t_first_stmt)=t_new_stmt; */
tree_stmt_iterator itor;
itor = tsi_start(t_body);
tsi_link_before(&itor, t_new_stmt, TSI_SAME_STMT);
}
Cheers!
/Björn Skoglund
code instrumentation in the tree structure
Hi everyone
I don't know if this is a development-list issue but I thought I'd try.
I'm writing a code instrumentation tool using the GEM
plugin-system (http://www.ecsl.cs.sunysb.edu/gem/) as a part of my
thesis project. I got it working in gcc-3.4 with a little help from the
GEM maintainer but I have realized I need to move to gcc-4 to get access
to the control-flow manipulation tools. Now my problem is that my code
which inserted function call statements does not work under the gcc-4
environment. the EXPR_STMT-symbol is gone for example. which makes the line
t_new_stmt = build_nt(EXPR_STMT, t_call);
cause compilation errors. Now, has the notion of statements been removed
in gcc-4, and in that case what has replaced it? I am quite confused at
the moment so if something doesn't make sense I'd be very happy with any
kind of explanation that makes me understand again. The following piece
of code is what I'm working with at the moment. It compiles but doesn't
really cause anything to happen when run.
void ci_insert_call(tree t_func, const char* func_name, tree args) {
tree t_func_decl;
tree t_body;
tree t_first_stmt;
tree t_call;
tree t_new_stmt;
t_body=DECL_SAVED_TREE(t_func); // COMPOUND_STMT
/* t_first_stmt = COMPOUND_BODY(t_body); */
gem_find_symtab(&t_func_decl, func_name);
t_call=build_function_call(t_func_decl, args);
t_new_stmt = build_nt(CALL_EXPR, t_call);
/* TREE_CHAIN(t_new_stmt)=TREE_CHAIN(t_first_stmt); */
/* TREE_CHAIN(t_first_stmt)=t_new_stmt; */
tree_stmt_iterator itor;
itor = tsi_start(t_body);
tsi_link_before(&itor, t_new_stmt, TSI_SAME_STMT);
}
Cheers!
/Björn Skoglund
LIBGCC maintainers appointed
I am pleased to announce that the GCC Steering Committee has appointed the following individuals to maintain various portions of the libgcc infrastructure: Ian Lance Taylor as maintainer of libgcc2.[ch] and fp-bit.[ch], Joseph Myers as maintainer of soft-fp, and Jason Merrill as maintainer of unwind and gthr. Please join me in congratulating Ian, Joseph, and Jason. Ian, Joseph, and Jason, please update your listings in the MAINTAINERS file. Also, the GCC Steering Committee would like to clarify that build machinery maintainers are authorized to review and approve patches to libgcc build machinery. Happy hacking! David
how to change avr maintainer ?
Hi All. Right now the AVR port have two maintainers Denis Chertykov and Marek Michalkiewicz. The AVR community ask me to add Anatoly Sokolov <[EMAIL PROTECTED]> as avr maintainer and Marek asked to remove him. How to do that ? Denis.
Re: GCC testsuite timeout question (gcc.c-torture/compile/20001226-1.c)
> From: Rask Ingemann Lambertsen <[EMAIL PROTECTED]> > >In case it isn't obvious, I have little or no clue about tcl, expect and > dejagnu. The only time that I've had success in modifying the timeout was by > adding this to /usr/share/dejagnu/baseboards/unix.exp: > > set_board_info gcc,timeout 5400 I am not sure what the 'right' way to do this is. I wound up editing /usr/share/dejagnu/remote.exp to change 'set timeout 300' to 'set timeout 2000' and I edited /usr/share/dejagnu/config/unix.exp to change 'set status [remote_wait $dest 300]' to 'set status [remote_wait $dest 2000]' It may not be the right way to do it but it has worked for me. Steve Ellcey [EMAIL PROTECTED]
Re: how to change avr maintainer ?
On Tue, Sep 05, 2006 at 11:55:03PM +0400, Denis Chertykov wrote: > Right now the AVR port have two maintainers Denis Chertykov > and Marek Michalkiewicz. > > The AVR community ask me to add Anatoly Sokolov <[EMAIL PROTECTED]> as avr > maintainer and Marek asked to remove him. > How to do that ? The SC has to approve it; I forwarded your message to the SC list.
gcc-4.2.0-20060902 stops compiling jikes-1.22
The snapshot gcc-4.2.0-20060902 stops compiling jikes-1.22.tar.bz2. It doesn't ocurr with gcc-3.3.6, gcc-4.1.2-20060901 and gcc-4.0.4-20060831, they are OK. $ gcc -v Using built-in specs. Target: i486-slackware-linux Configured with: ./configure --prefix=/tools/gcc42 --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 4.2.0 20060902 (experimental) export CFLAGS="-Os -fomit-frame-pointer -march=i486 -Wall -pipe" export LDFLAGS="-Xlinker -s" export LD_LIBRARY_PATH=/tools/gcc42/lib ./configure CC=gcc CFLAGS="$CFLAGS" LDFLAGS="$LDFLAGS" --prefix=/tools/jikes make && make install set.cpp:17: error: variable-sized object 'SymbolSet::primes' may not be initialized set.cpp:17: error: storage size of 'SymbolSet::primes' isn't constant set.cpp:191: error: variable-sized object 'SymbolMap::primes' may not be initialized set.cpp:191: error: storage size of 'SymbolMap::primes' isn't constant make[2]: *** [set.o] Error 1 make[2]: Leaving directory . make[1]: *** [all] Error 2 make[1]: Leaving directory . make: *** [all-recursive] Error 1 Good good good bye Obtenga su E-mail GRATUITO en http://www.clanomega.com ___ Get your own Web-based E-mail Service at http://www.zzn.com
