Is it possible to avoid instrumenting functions
(-finstrument-functions) if they are in a particular section?
On 04/13/2016 07:01 AM, Cristina Georgiana Opriceana wrote:
Hello,
I bring to your attention SafeStack, part of a bigger research project
- CPI/CPS [1], which offers complete protection against stack-based
control flow hijacks. I am interested in developing SafeStack for GCC
and I would like to
Snapshot gcc-4.9-20160427 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20160427/
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
On Wed, Apr 27, 2016 at 12:30 AM, Andrew Pinski wrote:
> On Fri, Apr 22, 2016 at 8:37 PM, Zhangjian (Bamvor)
> wrote:
>> Hi, Yury
>>
>>
>> On 2016/4/6 6:44, Yury Norov wrote:
>>>
>>> There are about 20 failing tests of 782 in lite scenario.
>>> float_bessel
>>> float_exp_log
>>> float_iperb
>>> f
On Wed, Apr 27, 2016 at 4:39 PM, Uros Bizjak wrote:
> On Wed, Apr 27, 2016 at 4:26 PM, Ilya Enkovich wrote:
>
>> > X86_TUNE_GENERAL_REGS_SSE_SPILL: Try to spill general regs to SSE
>> > regs
>> instead of memory.
>> >
>> > I tried enabling the above tuning with -march=bdv
On Wed, Apr 27, 2016 at 4:26 PM, Ilya Enkovich wrote:
>>> >> > X86_TUNE_GENERAL_REGS_SSE_SPILL: Try to spill general regs to SSE
>>> >> > regs
>>> >> instead of memory.
>>> >> >
>>> >> > I tried enabling the above tuning with -march=bdver4 -Ofast -mtune-
>>> >> ctrl=general_regs_sse_spill.
>>> >>
2016-04-27 17:06 GMT+03:00 Kumar, Venkataramanan :
> Hi,
>
>> -Original Message-
>> From: Ilya Enkovich [mailto:enkovich@gmail.com]
>> Sent: Wednesday, April 27, 2016 5:35 PM
>> To: Kumar, Venkataramanan
>> Cc: vmaka...@redhat.com; gcc@gcc.gnu.org; Uros Bizjak
>> (ubiz...@gmail.com)
>
On Wed, Apr 27, 2016 at 4:54 PM, David Malcolm wrote:
> On Wed, 2016-04-27 at 12:34 +0300, Cristina Georgiana Opriceana wrote:
>> Hello,
>>
>> I tried to add a new global declaration of a pointer and I expected
>> to
>> see it in varpool nodes, but it does not appear there.
>>
>> ustackptr = build
Hi,
> -Original Message-
> From: Ilya Enkovich [mailto:enkovich@gmail.com]
> Sent: Wednesday, April 27, 2016 5:35 PM
> To: Kumar, Venkataramanan
> Cc: vmaka...@redhat.com; gcc@gcc.gnu.org; Uros Bizjak
> (ubiz...@gmail.com)
> Subject: Re: Question on TARGET_MMX and
> X86_TUNE_GENERAL
On Wed, 2016-04-27 at 12:34 +0300, Cristina Georgiana Opriceana wrote:
> Hello,
>
> I tried to add a new global declaration of a pointer and I expected
> to
> see it in varpool nodes, but it does not appear there.
>
> ustackptr = build_decl (UNKNOWN_LOCATION,
> VAR_DE
Hi all,
the web page at http://gcc.gnu.org still links to the gcc 7 status
report from March 10, but there is a more recent one from April 15.
Could this please be updated?
Cheers,
Martin Reinecke
2016-04-27 14:35 GMT+03:00 Kumar, Venkataramanan :
> Hi ,
>
>> -Original Message-
>> From: Ilya Enkovich [mailto:enkovich@gmail.com]
>> Sent: Tuesday, April 26, 2016 7:09 PM
>> To: Kumar, Venkataramanan
>> Cc: vmaka...@redhat.com; gcc@gcc.gnu.org; Uros Bizjak
>> (ubiz...@gmail.com)
>>
Status
==
GCC 6.1 has been released, branches/gcc-6-branch now identifies itself as
6.1.1 and is now open again under the usual release branch rules (regression
fixes and documentation fixes only).
The next release, 6.2, should be released in about two or three months
from now, unless somethin
After slightly more than a year since last major GCC release, we are proud
to announce new major GCC release, 6.1.
GCC 6.1 is a major release containing substantial new
functionality not available in GCC 5.x or previous GCC releases.
The C++ frontend now defaults to C++14 standard instead of C++9
Hi ,
> -Original Message-
> From: Ilya Enkovich [mailto:enkovich@gmail.com]
> Sent: Tuesday, April 26, 2016 7:09 PM
> To: Kumar, Venkataramanan
> Cc: vmaka...@redhat.com; gcc@gcc.gnu.org; Uros Bizjak
> (ubiz...@gmail.com)
> Subject: Re: Question on TARGET_MMX and
> X86_TUNE_GENERAL_R
Hello,
I tried to add a new global declaration of a pointer and I expected to
see it in varpool nodes, but it does not appear there.
ustackptr = build_decl (UNKNOWN_LOCATION,
VAR_DECL, get_identifier ("ustackptr"),
build_pointer_type(void_
On Fri, Apr 22, 2016 at 8:37 PM, Zhangjian (Bamvor)
wrote:
> Hi, Yury
>
>
> On 2016/4/6 6:44, Yury Norov wrote:
>>
>> There are about 20 failing tests of 782 in lite scenario.
>> float_bessel
>> float_exp_log
>> float_iperb
>> float_power
>> float_trigo
>> pipeio_1
>> pipeio_3
>> pipeio_5
>> pipei
17 matches
Mail list logo