On Wed, 25 Feb 2015, Sandra Loosemore wrote:
>> Patch is a part of a series which is waiting for additional steering
>> committee approval due to copyright and a license.
> I don't imagine the documentation for *features already committed*
> needs to wait for steering committee approval; per the G
Snapshot gcc-4.9-20150225 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20150225/
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
So the steering committee has agreed to include the MPX runtime in GCC.
The runtime bits are a necessary component to actually make use of the
MPX capabilities.
GCC is a downstream consumer of the core runtime and the canonical
repository for the wrapper subpart of that runtime.
The quest
I'm pleased to announce that Kirill Yukhin has been appointed as the
maintainer for the vector ISA extensions for the x86 port.
Kirill, if you could add yourself to the MAINTAINERS file for the
additional role, it would be appreciated.
Thanks,
Jeff
I'm pleased to announce Ilya Enkovich has been appointed as the
maintainer for the generic bounded pointer infrastructure, the MPX
implementation of bounded pointers and the MPX runtime for GCC.
Ilya, if you could add yourself to the MAINTAINERS file in the
additional roles, it would be apprec
it is a good policy to do a run with full checking every once in a
while. it is easy to have some garbage sneak in.df is particularly
sensitive to bad rtl so that was my first suggestion.i had forgotten
that df (as well as a lot of the infrastructure) does not work very late.
On 02/25
Am 02/24/2015 um 07:33 PM schrieb Kenneth Zadeck:
when i suggested that you do a build with all of the checking turned on, i
wanted you to this without you new code in it.there is a good possibility
that the problem is that your port is generating bad rtl.
Ah, ok. This actually revealed an
On 02/25/2015 09:47 AM, Ilya Enkovich wrote:
2015-02-25 19:16 GMT+03:00 Sandra Loosemore :
On 02/25/2015 12:56 AM, Ilya Enkovich wrote:
2015-02-24 19:47 GMT+03:00 Sandra Loosemore :
Poking around, I see that the -fcheck-pointer-bounds and various -fchkp-*
options are listed in c-family/c.op
Compiling with -flto-partition=none succeeds,
however increases compilation time significantly.
One interesting thing is that even the failed compile
produces an executable that works. Is that normal?
Should I really attach the ipa-cgraph dump to the bug report?
The file is 945M big, 27M compress
2015-02-25 19:16 GMT+03:00 Sandra Loosemore :
> On 02/25/2015 12:56 AM, Ilya Enkovich wrote:
>>
>> 2015-02-24 19:47 GMT+03:00 Sandra Loosemore :
>>>
>>>
>>> Poking around, I see that the -fcheck-pointer-bounds and various -fchkp-*
>>> options are listed in c-family/c.opt, but they are not listed in
On 02/25/2015 12:56 AM, Ilya Enkovich wrote:
2015-02-24 19:47 GMT+03:00 Sandra Loosemore :
Poking around, I see that the -fcheck-pointer-bounds and various -fchkp-*
options are listed in c-family/c.opt, but they are not listed in the GCC
manual. The section on intrinsics is not enough, by itse
> Hi,
>
> I have problems compiling xalan as part of spec2006 benchmark for aarch64,
> both native and cross.
> The issue arises when both -flto and -fprofile-generate are enabled during
> LTO.
> Compiling with the same flags for x86 has no problem.
> Also other projects for aarch64 compile with
12 matches
Mail list logo
