Re: GCC build on darwin12.3

Are you using Mac ports for gmp/mpfr/mpc libraries? I see that you have "-L/opt/local/lib" on you path. I had the same issue and as I recall it was related to installing iconv mac port package and incompatibility of iconv.h header files. I switched to building gmp/mpfr/mpc from sources and not

Re: gcc build on FC18 and automake 1.11

On 3/27/13 5:27 PM, Ian Lance Taylor wrote: You could install autoconf 2.64, which is the version used to build the configure files in the GCC tree. I am using 2.64 (installed from the source). I also installed automake 1.11.1 from the source, but 'aclocal' (part of automake) is a perl scrip

gcc build on FC18 and automake 1.11

The latest Fedora Core 18 comes with automake 1.12.1 and perl 5.16.2. I installed and tried to use automake 1.11.1 for one of the GCC libraries, but got a warning from aclocal: main::scan_file() called too early to check prototype at /usr/local/bin/aclocal line 617. The latest 1.11.6 has the

gcc trunk target libraries do not build on Darwin 12.1

I am having trouble building the trunk om Mac OS X 10.8.1 (Darwin 12.1.0). Configuring target libraries fails with the following error (e.g. libatomic): configure:3477: checking for C compiler default output file name configure:3499: /eng/upc/dev/nenad/gcc-trunk/bld/./gcc/xgcc -B/eng/upc/dev/n

Building gcc on Ubuntu 11.10

Has anybody tried to build 4.7 on Ubuntu 11.10 system. I am getting the following linking problem (no special configure switches): /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cann

"-g" option enables var_tracking and long compilation on Darwin - x86_64-apple-darwin10.8.0

I have a test program written in UPC that takes a long time to compile on Mac OS X. This is caused by the var_tracking code that I think is getting erroneously enabled for no-optimization case - only "-g" option is used on a command line. When process_options (in toplevel.c) is called, flag_va

Re: adding an argument for test execution in testsuite

ronment. Notice that ${tool}_load already accepts arguments that can be passed to the program. Nenad On 5/4/11 3:32 PM, Janis Johnson wrote: On 05/04/2011 11:21 AM, Nenad Vukicevic wrote: It seems that I fixed my problem by defining remote_spawn procedure (and fixing the order of loading librarie

Re: adding an argument for test execution in testsuite

guments is getting set before dg-test is being called. I used a simple string compare to see if dynamic threads are required. So far it works as expected. Thank you. Nenad On 5/4/2011 10:18 AM, Ian Lance Taylor wrote: Nenad Vukicevic writes: Thank you for your response. I am trying to write some

Re: adding an argument for test execution in testsuite

On 5/3/2011 3:47 PM, Ian Lance Taylor wrote: There is no support for passing options to a test in the dg framework. You would have to write your own Tcl code to do that. Note that such tests are somewhat discouraged because not all remote execution environments support passing command line argum

adding an argument for test execution in testsuite

Is it possible to add an argument to the test in the execution phase of the testsuite? I am looking into some test cases where number of threads to run must be provided on the invocation line of the test if not specified during the test compilation. Something that is similar to "dg-skip-if" syntax

Re: Two debug entries for one local variables, is it a bug in GCC or GDB

I reported something similar back in January: http://gcc.gnu.org/ml/gcc/2010-01/msg00054.html As I recall, GCC creates duplicates. Nenad On 7/8/10 7:33 PM, asmwarrior wrote: I have post this message to both GCC and GDB, because I'm not sure it is a bug in GDB or GCC. Hi, I have just find t

Re: dwarf2 - multiple DW_TAG_variable for global variable

DW_AT_type: <0x4d> <6c> DW_AT_external: 1 <6d> DW_AT_location: 9 byte block: 3 0 0 0 0 0 0 0 0 (DW_OP_addr: 0) in 4.4.1 and 4.5 releases. Any idea if this is a correct dwarf? Or must be treated as a duplicate somehow? Thanks, Nenad On 1/9/10 1:18 PM, J

Re: dwarf2 - multiple DW_TAG_variable for global variable

_label, declare_label, c_make_fname_decl, c_builtin_function, c_builtin_function_ext_scope, store_parm_decls_newstyle): Adjust bind callers. Jan, can you confirm that this is indeed the correct DWARF that is being generated. Thank you, Nenad On 1/4/10 11:34 PM, Nenad Vuk

dwarf2 - multiple DW_TAG_variable for global variable

I installed gcc-4.5-20091224 snapshot and noticed that for simple variable declaration I get two DW_TAG_variable dies in the object file. For example, the following code int x; main() {x=1;} generates (with -g -gdwarf2 -O0 switches): <1><54>: Abbrev Number: 4 (DW_TAG_variable) <55>