Re: GCC version bikeshedding

On Tue, Jul 22, 2014 at 08:44:41AM +0100, Richard Sandiford wrote: > So why > not just stick to the current scheme and have 5.0.0, 5.0.1, 5.0.2 etc.? Yes, why would we use a different numbering scheme now? There is no change in development / release planning, unless I missed something. Is this j

successfully built and installed GCC 4.9.1 armv7l-unknown-linux-gnueabihf

$ ../gcc-4.9.1/config.guess armv7l-unknown-linux-gnueabihf $ /opt/gcc/4.9.1/bin/gcc -v Using built-in specs. COLLECT_GCC=/opt/gcc/4.9.1/bin/gcc COLLECT_LTO_WRAPPER=/opt/gcc/4.9.1/libexec/gcc/arm-linux-gnueabihf/4.9.1/lto-wrapper Target: arm-linux-gnueabihf Configured with: ../gcc-4.9.1/con

Re: [Copyright transfer] What to do for copyright transfer to FSF for contracted changes?

On 07/21/14 10:19, Andre Vehreschild wrote: Hi, I am a freelancer contracted to fix some bugs in the fortran compiler. I understand that I need to transfer the copyright of that effort to the FSF. My client and me are willing to sign any paperwork needed for that. Unfortunately my client will be

Re: SC: New MIPS maintainers needed

On 07/22/14 06:56, Richard Sandiford wrote: I'll need to step down as MIPS maintainer this weekend in order to avoid a possible conflict of interest with a new job. SC: please could you appoint some new maintainers to take over? We'll get the process started. Stepping down doesn't require you

Re: What would it take to always force indirect inlining?

Hi, On Fri, Jul 18, 2014 at 03:31:23PM -0500, Daniel Santos wrote: > > On 07/18/2014 04:55 AM, Martin Jambor wrote: > >Hi, > > > >On Thu, Jul 17, 2014 at 12:26:43PM -0500, Daniel Santos wrote: > >>I've recently discovered that a function marked always_inline but > >>called by pointer won't always

Fw: Results for 4.9.1 (GCC) testsuite on i686-pc-linux-gnu

Dear GCC Team, As there are no test results listed in buildstats page for GCC (4.9.1) for i686-pc-linux-gnu, I am herewith sending the testsuite results. You can list them in buildstats page. Regards, Raghunath Lolur. On Tuesday, 22 July 2014 11:17 PM, Raghu L wrote: I would like to infor

PSU left at GNU Tools Cauldron

Hi all, We have a Dell Laptop PSU which was left at the GNU Tools Cauldron. If it is yours and you would like it back, please email me off list. Jeremy -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: jeremybennett Twitter: @jeremypbennett Email: jeremy.benn...@embecosm.co

Re: [GSoC] Question about the implementation of vec.h

> Yes, you need to use .create() to initialize vec instances. Thank you for the answer! -- Cheers, Roman Gareev.

Re: [GSoC] generation of Gimple code from isl_ast_node_block

It seems that the problem is solved now. Thank you! I've sent corresponding patches to gcc-patches. -- Cheers, Roman Gareev.

Re: [ARM] Is TARGET_UNIFIED_ASM still needed?

On 22/07/14 14:14, Kyrill Tkachov wrote: Hi all, In the arm backend we've got this TARGET_UNIFIED_ASM macro that is currently on for TARGET_THUMB2 with a comment that says: /* We could use unified syntax for arm mode, but for now we just use it for Thumb-2. */ I've been doing some work

Re: GCC version bikeshedding

On Sun, Jul 20, 2014 at 07:01:46PM +0200, Jakub Jelinek wrote: > Ian/Jason, is that your understanding too? In any case, we should mention > it on gcc.gnu.org/index.html, in develop.html and perhaps a few other spots. Also it'd be nice to create htdocs/gcc-5.0/changes.html, so we can start adding

Re: GCC version bikeshedding

On Tue, Jul 22, 2014 at 10:07 AM, Andreas Schwab wrote: > Richard Sandiford writes: > >> Andreas Schwab writes: >>> Richard Sandiford writes: So if x.y.z is __GNU__.__GNU_MINOR__.__GNU_PATCHLEVEL__ then the positions in the number stay the same but the meanings of __GNU_MINOR__ and >>

[ARM] Is TARGET_UNIFIED_ASM still needed?

Hi all, In the arm backend we've got this TARGET_UNIFIED_ASM macro that is currently on for TARGET_THUMB2 with a comment that says: /* We could use unified syntax for arm mode, but for now we just use it for Thumb-2. */ I've been doing some work converting the pre-UAL floating point mnemo

SC: New MIPS maintainers needed

I'll need to step down as MIPS maintainer this weekend in order to avoid a possible conflict of interest with a new job. SC: please could you appoint some new maintainers to take over? Matthew and Catherine (cc:ed) have been among the biggest contributors to the MIPS port recently and they said t

Re: [gomp4] Offloading wiki page

Hi! On Tue, 22 Jul 2014 13:30:55 +0200, Bernd Schmidt wrote: > On 07/22/2014 01:24 PM, Thomas Schwinge wrote: > > On Tue, 22 Jul 2014 13:06:19 +0200, Bernd Schmidt > wrote: > >> It says "Immutable Page", so I can't seem to edit it. > > > > Probably applies for your write access to any wiki

Re: [gomp4] Offloading wiki page

On 07/22/2014 01:24 PM, Thomas Schwinge wrote: > On Tue, 22 Jul 2014 13:06:19 +0200, Bernd Schmidt wrote: >> It says "Immutable Page", so I can't seem to edit it. > > Probably applies for your write access to any wiki page, and that's > because you've not been added to thw whitelist, >

Re: [gomp4] Offloading wiki page

Hi! On Tue, 22 Jul 2014 13:06:19 +0200, Bernd Schmidt wrote: > On 07/21/2014 09:07 PM, Ilya Verbin wrote: > > I've created a wiki page about offloading. Any improvements are welcome. Guys, thanks for setting this up so quickly! > It says "Immutable Page", so I can't seem to edit it. Probably

Notes from GNU Cauldron 2014

First of all, thanks to the organisers and the speakers for a very enjoyable and informative event. I took notes during many of the talks and someone suggested I share these notes to the list in case anyone is interested. I'm afraid I missed the steering committee Q+A and didn't take notes on the r

Re: [gomp4] Offloading wiki page

On 07/21/2014 09:07 PM, Ilya Verbin wrote: I've created a wiki page about offloading. Any improvements are welcome. It says "Immutable Page", so I can't seem to edit it. Anyway, here are my thoughts on the configure/make changes (should go into the TODO section): The host and offload compil

Re: Question for ARM person re asm_fprintf

Hi David, On 22/07/14 02:46, David Wohlferd wrote: I have been looking at asm_fprintf in final.c, and I think there's a design flaw. But since the change affects ARM and since I have no access to an ARM system, I need a second opinion. asm_fprintf allows platforms to add support for new format

Re: GCC version bikeshedding

Richard Sandiford writes: > Andreas Schwab writes: >> Richard Sandiford writes: >>> So if x.y.z is __GNU__.__GNU_MINOR__.__GNU_PATCHLEVEL__ then the positions >>> in the number stay the same but the meanings of __GNU_MINOR__ and >>> __GNU_PATCHLEVEL__ change. >> >> There is no change in meaning

Re: GCC version bikeshedding

Andreas Schwab writes: > Richard Sandiford writes: >> So if x.y.z is __GNU__.__GNU_MINOR__.__GNU_PATCHLEVEL__ then the positions >> in the number stay the same but the meanings of __GNU_MINOR__ and >> __GNU_PATCHLEVEL__ change. > > There is no change in meaning. Sure there is, in terms of the re

Re: GCC version bikeshedding

Richard Sandiford writes: > So if x.y.z is __GNU__.__GNU_MINOR__.__GNU_PATCHLEVEL__ then the positions > in the number stay the same but the meanings of __GNU_MINOR__ and > __GNU_PATCHLEVEL__ change. There is no change in meaning. .. stays the same. Andreas. -- Andreas Schwab, sch...@linux-m