Re: broken link on this page https://gcc.gnu.org/gcc-7/changes.html for link to "Profile Mode" page:

[Jonathan Wakely]

On 5 August 2017 at 21:58, Gerald Pfeifer wrote:
> On Fri, 4 Aug 2017, Jonathan Wakely wrote:
>> Thanks for letting us know, I've fixed the link.
>
> Thanks, Jonathan.
>
> https://gcc.gnu.org/onlinedocs/gcc-7.1.0/libstdc++/manual/manual/profile_mode.html
>^
>
> Should we do something about "manual/manual" in the above, though?
>
> Gerald

It's been like that in every release for years. I'm not worried about it.

Re: GCJ wiki page

[Jonathan Wakely]

On 7 August 2017 at 02:29, Vincent Lefevre wrote:
> Hi,
>
> The GCJ wiki page https://gcc.gnu.org/wiki/GCJ appears to be very
> obsolete. According to this page, GCJ is part of GCC, but AFAIK,
> GCJ has been removed from GCC.

Thanks, I've updated the page.

Re: [PATCH] Write dependency information (-M*) even if there are errors

[Segher Boessenkool]

Hi!

Patches should go to gcc-patches.

Just a trivial remark:

> --- gcc/c-family/c-opts.c (revision 250514)
> +++ gcc/c-family/c-opts.c (working copy)
> @@ -1152,8 +1152,11 @@
>  {
>FILE *deps_stream = NULL;
>  
> -  /* Don't write the deps file if there are errors.  */
> -  if (cpp_opts->deps.style != DEPS_NONE && !seen_error ())
> +  /* Note that we write the dependencies even if there are errors. This is
> + useful for handling outdated generated headers that now trigger errors
> + (for example, with #error) that would be resolved by re-generating
> + them. In a sense this complements -MG. */

Two spaces after a full stop (all three times).


Segher

Re: An internal GCC compiler error when compiling GCC 7.x with GCC 6.x and 4.x

[Martin Liška]

On 07/30/2017 05:08 AM, Ethin Probst wrote:
> Hello all,
> I was trying to build GCC 7.1.0 on OpenSuse 42.1 when it encountered
> an internal error. The error is thrown, for lack of a better word, in
> both 4.x and 6.x.
> I would have submitted a bug report on the GCC bug tracker except for
> the fact that I don't have all the information needed, so thought I
> should report it here. What I don't have is the options given when GCC
> was configured/built (for the system host compiler) and the
> preprocessed file (*.i*) that triggers the bug. I'll give the rest
> here, though.
> The exact version of GCC that triggered the internal error was both
> version gcc (SUSE Linux) 4.8.5 and gcc-6 (SUSE Linux) 6.2.1 20160826
> [gcc-6-branch revision 239773].
> The system type is a Linode VPS. Kernel and node names are Linux,
> kernel release is 4.9.15-x86_64-linode81, kernel version is #1 SMP Fri
> Mar 17 09:47:36 EDT 2017, and machine, processor, and hardware
> platform are all x86_64.
> From what I can gather, the exact command that triggered the error was:
> /home/ethin/gccbuild/./gcc/xgcc -B/home/ethin/gccbuild/./gcc/
> -B/usr/local/x86_64-pc-linux-gnu/bin/
> -B/usr/local/x86_64-pc-linux-gnu/lib/ -isystem
> /usr/local/x86_64-pc-linux-gnu/include -isystem
> /usr/local/x86_64-pc-linux-gnu/sys-include   -g0 -fcompare-debug= -g
> -O2 -O2  -g -O2 -DIN_GCC -fPIC   -W -Wall -Wno-narrowing
> -Wwrite-strings -Wcast-qual -Wno-format -Wstrict-prototypes
> -Wmissing-prototypes -Wold-style-definition  -isystem ./include
> -fpic -mlong-double-80 -DUSE_ELF_SYMVER -g -DIN_LIBGCC2
> -fbuilding-libgcc -fno-stack-protector   -fpic -mlong-double-80
> -DUSE_ELF_SYMVER -I. -I. -I../.././gcc -I../../../gcc-7.1.0/libgcc
> -I../../../gcc-7.1.0/libgcc/. -I../../../gcc-7.1.0/libgcc/../gcc
> -I../../../gcc-7.1.0/libgcc/../include
> -I../../../gcc-7.1.0/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT
> -DHAVE_CC_TLS  -DUSE_TLS -o _addQQ.o -MT _addQQ.o -MD -MP -MF
> _addQQ.dep -DL_add -DQQ_MODE -c ../../../gcc-7.1.0/libgcc/fixed-bit.c
> -fvisibility=hidden -DHIDE_EXPORTS
> I configured the GCC 7.1.0 package with the command (from the
> $HOME/gccbuild directory):
> ../gcc-7.1.0/configure --enable-host-shared --enable-multiarch
> --enable-vtable-verify --disable-multilib --enable-threads
> --enable-tls --enable-__cxa_atexit --enable-gnu-indirect-function
> --enable-comdat --enable-initfini-array --enable-bootstrap
> --enable-languages=ada,brig,c,c++,fortran,go,jit,lto,objc,obj-c++
> --enable-libada --enable-libsanitizer --enable-libssp
> --enable-libquadmath --enable-libquadmath-support --enable-libgomp
> --enable-libvtv --enable-default-pie --enable-default-ssp --enable-cld
> --enable-checking=all --disable-nls --enable-fixed-point
> --with-long-double-128 --enable-linker-build-id
> --enable-gnu-unique-object --enable-lto
> --enable-canonical-system-headers --enable-objc-gc
> --enable-liboffloadmic=target
> --with-build-config="bootstrap-debug-lean bootstrap-debug-lib
> bootstrap-debug-ckovw" --quiet CC=gcc-6 CXX=g++-6 CC_FOR_TARGET=gcc-6
> CXX_FOR_TARGET=g++-6 GCC_FOR_TARGET=gcc-6
> GFORTRAN_FOR_TARGET=gfortran-6
> The command I used to configure GCC without the GCC 6.x installation
> (so it used 4.8.5, the default) was:
> ../gcc-7.1.0/configure --enable-host-shared --enable-multiarch
> --enable-vtable-verify --disable-multilib --enable-threads
> --enable-tls --enable-__cxa_atexit --enable-gnu-indirect-function
> --enable-comdat --enable-initfini-array --enable-bootstrap
> --enable-languages=ada,brig,c,c++,fortran,go,jit,lto,objc,obj-c++
> --enable-libada --enable-libsanitizer --enable-libssp
> --enable-libquadmath --enable-libquadmath-support --enable-libgomp
> --enable-libvtv --enable-default-pie --enable-default-ssp --enable-cld
> --enable-checking=all --disable-nls --enable-fixed-point
> --with-long-double-128 --enable-linker-build-id
> --enable-gnu-unique-object --enable-lto
> --enable-canonical-system-headers --enable-objc-gc
> --enable-liboffloadmic=target
> --with-build-config="bootstrap-debug-lean bootstrap-debug-lib
> bootstrap-debug-ckovw" --quiet
> The exact output of the command was as follows:
> In file included from ../../../gcc-7.1.0/libgcc/fixed-bit.c:55:0:
> ../../../gcc-7.1.0/libgcc/fixed-bit.h:64:1: error: unable to emulate 'QQ'
>  typedef  _Fract QQtype  __attribute__ ((mode (QQ)));
>  ^~~
> ../../../gcc-7.1.0/libgcc/fixed-bit.h:65:1: error: unable to emulate 'UQQ'
>  typedef unsigned _Fract UQQtype __attribute__ ((mode (UQQ)));
>  ^~~
> ../../../gcc-7.1.0/libgcc/fixed-bit.h:66:1: error: unable to emulate 'HQ'
>  typedef  _Fract HQtype  __attribute__ ((mode (HQ)));
>  ^~~
> ../../../gcc-7.1.0/libgcc/fixed-bit.h:67:1: error: unable to emulate 'UHQ'
>  typedef unsigned _Fract UHQtype __attribute__ ((mode (UHQ)));
>  ^~~
> ../../../gcc-7.1.0/libgcc/fixed-bit.h:68:1: error: unable to emulate 'HA'
>  typedef  _Fract HAtype  __attribute__ ((mode (HA)));
>  ^~~
> ../../../gcc-7.1.0/lib

Re: An internal GCC compiler error when compiling GCC 7.x with GCC 6.x and 4.x

[Joseph Myers]

On Mon, 7 Aug 2017, Martin Liška wrote:

> On 07/30/2017 05:08 AM, Ethin Probst wrote:

> > --enable-checking=all --disable-nls --enable-fixed-point

> > In file included from ../../../gcc-7.1.0/libgcc/fixed-bit.c:55:0:
> > ../../../gcc-7.1.0/libgcc/fixed-bit.h:64:1: error: unable to emulate 'QQ'

> I can take a look, but please create a bug issue and try to isolate *.i* 
> files by adding -E to the GCC invocation that causes the problem.

I think it's clear enough from the above that the problem is the use of 
--enable-fixed-point for a target that doesn't support that feature (i.e. 
anmything other than ARM and MIPS).

(As I previously noted 
 it's 
unfortunate that the fixed-point support requires so much target-specific 
code rather than being based on GIMPLE lowering.  But as that's the 
present situation, --enable-fixed-point on targets without the 
target-specific code isn't really useful.)

-- 
Joseph S. Myers
jos...@codesourcery.com

GNU Tools Cauldron 2017, September 8-10, 2017

[Jan Hubicka]

Hello,
I would like to remind you of the upcoming GNU Tools Cauldron meeting in Prague
September 8-10.  https://gcc.gnu.org/wiki/cauldron2017 (in 5 weeks!)

At the present we still have 83 registered participants and the room capacity
is bit over 100 seats. If you want to participate, please register soon.  We
also have 35 registered proposals for talks and BoFs which will make it a busy
3 days. (those which were submitted with title and abstract are now available
at https://gcc.gnu.org/wiki/cauldron2017#Abstracts)

Because there will be two tracks, we are still open for last minute talk and
BoF proposals.

If you have a topic that you would like to present, please submit an abstract
describing what you plan to present. We are accepting three types of
submissions:

Prepared presentations: demos, project reports, etc.
BoFs: coordination meetings with other developers.
Tutorials for developers. No user tutorials, please. 

To register your abstract, send e-mail to tools-cauldron-ad...@googlegroups.com

Your submission should contain the following information:

Title:
Authors:
Abstract: 

If you intend to participate, but not necessarily present, please let us know
as well. Send a message to tools-cauldron-ad...@googlegroups.com stating your
intent to participate. Please indicate your affiliation, dietary requirements
and t-shirt size. 

Looking forward to see you soon in Prague,
Jan