George R Goffe | 24 Apr 05:24 2014
Picon

Need some help with a possible bug


Hi,

I'm trying to build the latest gcc and am getting a message from the process "collect2: error: ld returned 1
exit status" for this library /usr/lsd/Linux/lib/libgmp.so. Here's the full msg:
"/usr/lsd/Linux/lib/libgmp.so: could not read symbols: File in wrong format"

When I use the file command on this library, I get this:

file libgmp.so.10.2.0
libgmp.so.10.2.0: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked, 
BuildID[sha1]=c8ca89cca80d669102f5b3e8e077b5d00f47bf78, not stripped

I'm running Fedora 19 X86_64 and, as far as I know, building for this architecture. I just built the latest
gmp, mpc, mpfr hoping that that was the problem but I still get the msg.

Here's a more elaborate snip of the build log. I have the complete log if it's needed.

Thanks,

George...

file libgmp.so.10.2.0
libgmp.so.10.2.0: ELF 64-bit LSB shared object, x86-64, version 1 
(SYSV), dynamically linked, 
BuildID[sha1]=c8ca89cca80d669102f5b3e8e077b5d00f47bf78, not stripped

make[8]: Leaving directory 
`/sdc1/exphome/clipper/export/home/tools/gcc/obj-i686-pc-linux-gnu/
(Continue reading)

gccadmin | 24 Apr 00:37 2014
Picon

gcc-4.9-20140423 is now available

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

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

You'll find:

 gcc-4.9-20140423.tar.bz2             Complete GCC

  MD5=9ec9799d622a9828cbe6970e2e002f97
  SHA1=f9f66b8c2ce3ee78b117992f061d760af22d8171

Diffs from 4.9-20140416 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.9
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.

Rainer Emrich | 23 Apr 11:33 2014
Picon

gcc-4.9.0 manual


Not Found

The requested URL /onlinedocs/gcc-4.9.0/libstdc++-api.pdf.gz was not found on
this server.

Apache Server at gcc.gnu.org Port 80
Kenneth Zadeck | 22 Apr 21:28 2014

reviewers for wide int.

Richi,

David Edelsohn said that I should talk to you about appointing reviewers 
for wide-int.    While I think that it may not be necessary to have any 
reviewers for wide-int in the long term, I think that it would be useful 
to make Richard Sandiford, Mike Stump and myself reviewers at least for 
this release cycle.

While of course one hopes that there will be no issues with wide-int, a 
change of this size will have some pain no matter how well we have 
tested it.  Having three reviewers will assure problems are resolved 
quickly.

Thanks,

Kenny

Prathamesh Kulkarni | 22 Apr 18:39 2014
Picon

[GSoC] Generating patterns from meta-description

Hi,
    Thank-you for selecting me for GSoC 2014, I am looking forward to
working with GCC community. I am grateful to Richard Biener and Diego Novillo
for choosing to mentor me for this project. Unfortunately, I couldn't
reply last week because I am in the middle of university exams, I
apologize for that.

* Time Commitments:
I have university exams up-to 5th May, and couple of exams on 24th may
and 27th may. Thereafter I am completely free, and can commit up-to
50 hours per week on average.

* Few questions regarding genmatch:

a) Lexical analysis and Parsing:
I believe this is already in place. We would continue with
hand-written recursive descent parser.

b) Intermediate representations:
For representing "matching" operands
we will need to use a decision tree (I am not yet decided on how it would be
implemented). For "simplification" operands, we can use AST (struct operand).

For example:
(match_and_simplify
  (negate (negate  <at> 0))
   <at> 0)

(match_and_simplify
  (negate (bit_not  <at> 0))
(Continue reading)

Solal | 22 Apr 18:38 2014

C PreProcessor GCC-specific features ideas.

I've got ideas for improve the preprocessor with specific features.

The basic idea is to make the preprocessing language a complete
programming language.
That can be useful for includes things like Autotools and advanced
Makefiles directly in the source code, and have just a tiny Makefile for
compile.

0. Multiple defines on one variable.
The "constants" will be transformed in "variables".

1. Assertions
#assert <CONDITION> <COMMAND-TO-EXECUTE-CONDITION-IS-FALSE>
will be transformed in :
#if !<CONDITION>
#<CMD>
#endif
(And will be of course re-preprocessed.)

2. Calculating
#calculate <VAR> <CALCUL>
will be transformed in :
#define <VAR> <RESULT>
(And will be of course re-preprocessed.)
Example :
#calculate N 1+1
will be transformed in :
#define N 2
(That can works with any type : bools, etc.)

(Continue reading)

Jakub Jelinek | 22 Apr 15:19 2014
Picon

GCC 4.9.1 Status Report (2014-04-22)

Status
======

GCC 4.9.0 has been released, the branch is now open again under the usual
release branch rules (regression fixes and documentation fixes only).
The next release, 4.9.1, should be released in about two or three months
from now, unless something very urgent forces us to release earlier.

Quality Data
============

Priority          #   Change from Last Report
--------        ---   -----------------------
P1                0      0
P2               78   +  2
P3               17   + 11
--------        ---   -----------------------
Total            95   + 13

Previous Report
===============

http://gcc.gnu.org/ml/gcc/2014-04/msg00091.html

The next report will be sent by Joseph.

Jakub Jelinek | 22 Apr 15:10 2014
Picon

GCC 4.9.0 Released

One year and one month passed from the time when the last major version
of the GNU Compiler Collection has been announced, so it is the time again
to announce a new major GCC release, 4.9.0.

GCC 4.9.0 is a major release containing substantial new
functionality not available in GCC 4.8.x or previous GCC releases.

The Local Register Allocator, introduced in GCC 4.8.0 for ia32 and
x86-64 targets only, is now used also on the Aarch64, ARM, S/390
and ARC targets by default and on PowerPC and RX targets optionally.

There have been substantial improvements to C++ devirtualization
and various scalability bottlenecks in the interprocedural optimizations
and LTO have been fixed.

Support for various C++14 additions have been added to the C++ Front End,
on the standard C++ library side the most important addition is
support for the C++11 <regex>.

GCC 4.9.0 supports the OpenMP 4.0 standard for C and C++, and a partial
implementation of the Cilk Plus extension for data and task parallelism.

Various kinds of undefined behaviors in programs can be now diagnosed at
runtime through Undefined Behavior Sanitizer.

Support for the new little-endian powerpc64le-linux platform has been added,
which defaults to the new PowerPC ELFV2 ABI.
On x86-64 and ia32, support for the AVX-512 instruction set has been
implemented.

(Continue reading)

Joel Sherrill | 21 Apr 20:27 2014

multiple rtems targets __dso_handle not found

Hi

The cut and paste is from an sh-rtems C++ application link failure.
But the failure is happening on some h8300, m68k, powerpc, and
sh BSPs. Each BSP has its own linker script so if there is a mistake
in that due to age, then we could be missing some newer magic.
This is all with gcc 4.8.2 and binutils 2.24?

What are we missing that would have introduced this?

sh-rtems4.11-g++ -B../../../../../gensh1/lib/ -specs bsp_specs -qrtems
-m1 -O2 -g -Wall -Wmissing-prototypes -Wimplicit-function-declaration
-Wstrict-prototypes -Wnested-externs    -m1   -o cdtest.exe init.o main.o
main.o: In function `_static_initialization_and_destruction_0':
/users/joel/rtems-4.11-work/rtems-testing/rtems/build-sh-gensh1-rtems/sh-rtems4.11/c/gensh1/testsuites/samples/cdtest/../../../../../../../rtems/c/src/../../testsuites/samples/cdtest/main.cc:141:
undefined reference to `__dso_handle'
/users/joel/rtems-4.11-work/tools/lib/gcc/sh-rtems4.11/4.8.2/libstdc++.a(eh_globals.o):
In function `_static_initialization_and_destruction_0':
/users/joel/rtems-4.11-work/rtems-source-builder/rtems/build/sh-rtems4.11-gcc-4.8.2-newlib-cvs-head-1/build/sh-rtems4.11/libstdc++-v3/libsupc++/../../../../gcc-4.8.2/libstdc++-v3/libsupc++/eh_globals.cc:109:
undefined reference to `__dso_handle'
/users/joel/rtems-4.11-work/tools/lib/gcc/sh-rtems4.11/4.8.2/../../../../sh-rtems4.11/bin/ld:
cdtest.exe: hidden symbol `___dso_handle' isn't defined
/users/joel/rtems-4.11-work/tools/lib/gcc/sh-rtems4.11/4.8.2/../../../../sh-rtems4.11/bin/ld:
final link failed: Bad value

Thanks.

--

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill <at> OARcorp.com        On-Line Applications Research
(Continue reading)

gccadmin | 21 Apr 00:40 2014
Picon

gcc-4.10-20140420 is now available

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

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

You'll find:

 gcc-4.10-20140420.tar.bz2            Complete GCC

  MD5=f469781a32e9ffeeeefba92f2a84c191
  SHA1=b95c3da4ddfe3f13a507a4892c540a9e1127e94e

Diffs from 4.10-20140413 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.10
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.

Solal | 20 Apr 12:26 2014

The P language

Hello guys!
I've an idea of new frontend for GCC.
An Objective-D# language! But say "Objective-D Sharp" is quite long, so
I call it the P language (shouldn't be confused with the P language of
Amaya) because of the BCPL : we have the B and the C, so now that's the P.
The language should be just like Objective-C++, but :
-The two languages would be compatibler (for inherit Objective-C classes
from C++ classes and vice-versa, use C++ objects in Objective-C classes
and vice-versa, declare C++ namespaces in Objective-C declarations,
declare Objective-C declarations in C++ namespaces, use C++ class
features in Objective-C classes and vice-versa, uses C++ classes in
Objective-C classes and vice-versa, etc., etc., etc.)
-The C++ would be replaced by its successor D.
-The C# features would be available (and compatible with Objective-C and
D, as I defined in the first point). The .NET framework would be
replaced by .GNU.


Gmane