gmane.comp.gcc.devel

How to compare two text files? Using sed, cmp, diff, tr?

Georg-Johann Lay — 2012-05-26T10:01:58

The avr backend auto-generates parts of GCC's texi documentation,
namely the supported -mmcu= options, which are about 200.

To generate the texi a small C program is used to print the texi
to stdout, and that output is then compared against the already
existing doc/avr-mmci.texi

If the output is the same like in that file, nothing happens.

If the output differs from that file, the user (someone building the
avr compiler) is nagged to update the existing documentation so that
the documentation says in sync with the compiler.

The part of t-avr reads:

s-avr-mmcu-texi: gen-avr-mmcu-texi$(build_exeext)
$(RUN_GEN) $< | sed -e 's:\r::g' > avr-mmcu.texi
< at >if cmp -s $(srcdir)/doc/avr-mmcu.texi avr-mmcu.texi; then \
  $(STAMP) $< at >;\
else\
  echo >&2 ;\
  echo "***" >&2 ;\
  echo "*** Verify that you have permission to grant a" >&2 ;\
  echo "*** GFDL license for all new text in" >&2 ; \
  echo "*** avr-mmcu.texi,then copy it to $(srcdir)/doc/avr-mmcu.texi" 
 >&2 ; \
  echo "***" >&2 ;\
  fals

How to run a compiled C program?

Georg-Johann Lay — 2012-05-26T09:35:49

The avr backend auto-generates a part of the texi documentation by means 
  of a small C program. The relevant part of t-avr reads:

s-avr-mmcu-texi: gen-avr-mmcu-texi$(build_exeext)
$(RUN_GEN) $< | sed -e 's:\r::g' > avr-mmcu.texi


There was a problem report that the executable cannot be found.

When I wrote that I checked other uses of RUN_GEN (which is empty) in 
$(builddir)/gcc/Makefile that do calls like $(RUN_GEN) build/...

What is the correct way to call the executable? Add ./ like so?

s-avr-mmcu-texi: gen-avr-mmcu-texi$(build_exeext)
$(RUN_GEN) ./$< | sed -e 's:\r::g' > avr-mmcu.texi

Thanks for hints.

Johann

array bounds violation in caller-save.c : duplicate hard regs check added

DJ Delorie — 2012-05-25T23:18:54

If I apply this patch, which checks for duplicate hard registers within
-fira-share-save-slots, the following *-elf targets fail due to the assert:

bfin cris m32c rl78 rx sh sh64 v850

The following succeed:

frv h8300 i386 ia64 m32r mep mipsisa32 mipsisa64 mn10300 powerpc tx39

Without this patch, the failing targets eventually overflow the
call_saved_regs[] array (size FIRST_PSEUDO_REGISTER) and corrupt other
memory and data structures.  I originally had an assert for that
bounds check too, but this one caught all the cases sooner.

Can someone who knows more about IRA and this optimization explain if
and/or why duplicate hard regs are allowed at that point, and what if
any changes should be made to avoid the array overflow?

Thanks,
DJ


Index: caller-save.c
===================================================================
--- caller-save.c(revision 187842)
+++ caller-save.c(working copy)
< at >< at > -504,12 +504,13 < at >< at > setup_save_areas (void)
       struct saved_hard_reg *saved_reg2, *saved_reg3;
       in

gcc-4.6-20120525 is now available

2012-05-25T22:54:17

Snapshot gcc-4.6-20120525 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20120525/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 4.6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch revision 187900

You'll find:

 gcc-4.6-20120525.tar.bz2             Complete GCC

  MD5=b61c517c13afbfc306bebdfc33a2dd57
  SHA1=758ede6ec739e7bb8206f52c2a67dc937d761d10

Diffs from 4.6-20120518 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.6
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

[cxx-conversion] gcc-4.7.0 on Cygwin and MinGW32 with --enable-build-with-cxx successes

Aaron Gray — 2012-05-25T21:53:11

Hi,

Just to let people know I have succeeded in building gcc-4.7.0 with
--enable-build-with-cxx (All stages built as C++) on latest Cygwin
with GCC 4.5.3 and on MinGW32 with a rebuilt GCC 4.6.2 as the GCC
4.6.2 that came with MinGW was missing stdarg.h and stddef.h and
possibly other headers.

Many thanks,

Aaron

Should --with-build-sysroot be default to --with-sysroot?

H.J. Lu — 2012-05-25T18:33:48

When --with-sysroot is used to configure gcc, build will usually fail
if  --with-build-sysroot isn't set.  Should  --with-build-sysroot be set to
the same value as --with-sysroot by default if --with-sysroot is used?

gcc-4.5-20120524 is now available

2012-05-24T22:48:57

Snapshot gcc-4.5-20120524 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20120524/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_5-branch revision 187858

You'll find:

 gcc-4.5-20120524.tar.bz2             Complete GCC

  MD5=987f323fd9b4de2df8bec010a85f9253
  SHA1=aa914051b2e82adb1026a6f52f71665a05d4aa42

Diffs from 4.5-20120517 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.5
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

error: call of overloaded ‘foo(int)’ is ambiguous (0 vs null ptr)

Peter A. Felvegi — 2012-05-24T19:26:46

Hello,

I'm not sure whether this is standard behaviour or not; nonetheless I 
was quite surprised:

----8<----8<----8<----
void foo(long);
void foo(const char*);

void bar()
{
         foo(0);
         foo(0+0); // !
         foo(1-1); // !
         foo(1);
}
----8<----8<----8<----

The first call to foo() in bar() is ambiguous, all right (integral or 
ptr), but the next two (marked w/ !) ? Shouldn't the compiler know that 
0+0 or 1-1, etc can't be a null pointer? I tried all minor versions from 
4.4 to 4.8.

Somewhat connected question: if I use |-Wzero-as-null-pointer-constant 
to detect cases where 0 means null pointer, shouldn't there be a switch 
that forbids conversion from 0 to null ptr? I have a class that has 
operator() overloaded for size_t and for const char* (access elements by 
index or by name). All is well, except for the index 0: the call would 
be ambiguous. I tried to trick this with 0+0, etc, hence the whole post. 
0.0 works, though. Any better ideas? Explicit cast?

Supposing that I eli

[gimplefe] Merge from trunk, preparation for gimple testsuite

Diego Novillo — 2012-05-24T18:32:29

I've merged trunk into gimple-front-end (rev 187836).

I've added a manifest file to use with 
contrib/testsuite-management/validate_failures.py.

Sandeep, this will be useful when we start having more gimple tests (see 
http://gcc.gnu.org/wiki/Testing_GCC#Using_validate_failures.py).  You 
can use the validator to filter out all the "expected" FAIL/XPASS 
results from other parts of the testsuite.

I will be posting the patches to add the basic dejagnu support for 
having gimple tests.


Tested on x86_64.


Diego.

RMS to present at the Cauldron

Diego Novillo — 2012-05-24T16:44:05

For those of you attending the Cauldron meeting in Prague in July, RMS 
will be in town and will come by to give a talk on the first day of the 
meeting.

See you there!

how to disable __thiscall on MinGW-gcc-4.7.x ?

niXman — 2012-05-24T09:26:30

Hello!

http://gcc.gnu.org/ml/gcc-help/2012-05/msg00043.html

ping?

MPC/MPFR/GMP Usage

Andrew Burks — 2012-05-23T22:46:50

Hey everyone,

I'm using gcc-4.6.3 as part of the YAGARTO toolchain
(http://www.yagarto.de) with an STM32 ARM Cortex-M3 chip and was
wondering: what are the math libraries (MPC, MPFR, and GMP) used for?
Are they only required internally by gcc or are they implicitly added
to the final binary produced by gcc?

Thanks,
Andrew

Please Update the Installing GCC: Binaries Page

Colin Prior — 2012-05-23T22:37:48

Dear GCC

This is Colin Prior from Sunfreeware and UNIX Packages.

Please would you be good enough to update
http://gcc.gnu.org/install/binaries.html and add www.unixpackages.com
We as you will see from the Sunfreeware site we have removed the majority of
our packages including GCC (Solaris 2.5, 2.6 7, 8, and 9) over to the our
new site.

We may well be interested in doing some joint marketing with you. Let me
know if that's of interest.

BTW you may want to consider removing the Blastwave link as to all intents
and purposes that site has been dead for some time now.

Cheers

Colin


Colin Prior
Unix Packages
+1 206 310 4610
colin< at >unixpackages.com

mkconfig.sh incrementality?

Jay K — 2012-05-23T16:04:29

At the bottom of mkconfig.sh in 4.6.2 and 4.7.0:


# Avoid changing the actual file if possible.
if [ -f $output ] && cmp ${output}T $output >/dev/null 2>&1; then
    echo $output is unchanged >&2
    rm -f ${output}T
else
    mv -f ${output}T $output
fi

# Touch a stamp file for Make's benefit.
rm -f cs-$output
echo timestamp > cs-$output



Shouldn't the timestamp > cs-$output only be a) mainly if the other file updated, by the mv and b) corner case, if it doesn't exist?
Maybe rm -rf by the mv, and echo if not exist?



 - Jay

Effect of 'register' keyword on debug info

Rohit Arul Raj — 2012-05-23T13:22:57

Hello All,

I came across this issue while working with PowerPC GCC tool chain
v4.5.2 for e500mc(64bit)/e5500.
Test case compiled with '-O0 -g'.

/************************** Test Case ************************/
 1: int main()
 2: {
 3:int i=0;
 4:
 5:register float f1 = 55.77f;
 6:register double d1 = 22.99f;
 7:
 8:while (i <= 100)  -----------------------------------(A)
 9:{
10:i++;
11:f1 = (float)i / 177 + (float)d1;
12:d1 = (double)i / 155677 + f1;
13:i += (int)d1;
14:}
15: }

/**************** Debug Info *************************************/
 <2><5d>: Abbrev Number: 3 (DW_TAG_variable)
    <5e>   DW_AT_name        : f1
    <61>   DW_AT_decl_file   : 1
    <62>   DW_AT_decl_line   : 5
    <63>   DW_AT_type        : <0x7f>
    <67>   DW_AT_location    : 2 byte block: 90 3f (DW_OP_regx: 63)
 <2><6a>: Abbrev Number: 3 (DW_TAG_variable)
    <6b>   DW_AT_name        : d1
    <6e>   DW_AT_decl_file   : 1
    <6f>   DW_AT_decl_line   : 6
    <70>   DW_AT_type        : <0x86>
    <74>   DW

C++98/C++11 ABI compatibility for gcc-4.7

Jeffrey Yasskin — 2012-05-22T14:04:46

I've put together the following description of C++98/11 ABI
(in)compatibility, so people can tell which libraries need to be
recompiled. This is useful when you've bought a library that didn't
come with source code, and you're trying to figure out if you need to
buy a new version. I think this belongs on the Wiki somewhere, but I
wanted to run it by the list first to make sure it's accurate. You can
probably skip the first section, since it's just a description of how
to use the subsequent list.



This page explains how to identify when your pre-compiled library (.a
or .so) defines a symbol that has a different enough definition in
C++98 vs C++11 that it could cause runtime problems if it's linked
into a program compiled for the other version.

First, get a list of demangled symbols from your .a or .so:

$ (find . -name '*.a'|xargs nm -f posix; find . -name '*.so' | xargs
nm -f posix -D)|cut -f1 -d' '|LANG=C sort -u|c++filt|sort

(There may be better ways to get this list.)

Next, find instances in this lis

Enabling a function based on Language

Iyer, Balaji V — 2012-05-21T22:52:12

Hello Everyone,
Is there a #define in GCC that will turn on only for certain languages? I am trying to use build_array_ref but it is giving me a undefined reference for f951. This code that I am trying to use will ONLY execute  if we have a C/C++ code.  Is it possible for me to enclose this inside some #defines (or a combination of them)?

Any help is greatly appreciated!

Thanks,

Balaji V. Iyer.

cine castiga

2012-05-21T19:04:28

http://www.youtube.com/watch?feature=youtu.be&hl=ro&v=_Sl3Ox7RMnE
 To unsubscribe please send email to unsubscribe< at >cc.psd-prahova.ro

Problem of gfortran compilation with -O option

PERRONNET Alain — 2012-05-21T14:25:44

My program and subroutines are mainly written in fortran 77 with blanck 
common of different sizes.
The program contains the maximum byte declaration of the blanck common.
1% are written in C, compiled with gcc.

-bash->  gfortran -v
Utilisation des specs internes.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper
Target: x86_64-linux-gnu
Configuré avec: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 
4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs 
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.6 --enable-shared --enable-linker-build-id 
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--enable-gnu-unique-object --enable-plugin --enable-objc-gc 
--disable-werror --with-arch-32=i686 --with-tune=gener

gcc-4.8-20120520 is now available

2012-05-20T22:46:48

Snapshot gcc-4.8-20120520 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20120520/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 187696

You'll find:

 gcc-4.8-20120520.tar.bz2             Complete GCC

  MD5=bf2fa8dba870f9bfffe5f4a1047cf0e2
  SHA1=c32ac35d661b5e7714f2a76697f013556a4bb2ed

Diffs from 4.8-20120513 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.8
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

Failing bootstraps --with-build-config=bootstrap-lto

Toon Moene — 2012-05-20T19:23:51

Hi,

I have added a line to my "Failing bootstrap" mails, that indicates what 
configure options I passed.

For instance, the last entry reads (at the end):

Configured by: configure --prefix=/tmp/c --with-gnu-as --with-gnu-ld 
--enable-languages=c++ --with-build-config=bootstrap-lto 
--disable-libmudflap --disable-multilib --disable-nls --with-arch=native 
--with-tune=native

I hope this helps.  I still have to figure out how to include the target 
triple (probably x86_64-unknown-linux-gnu) in the subject.

Kind regards,