Hello,
-> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87210
This RFE is about providing gcc option(s) to eliminate information leakage
issues from programs. Information leakage via uninitialised memory has beena
chronic/recurring issue across all software. They are found quite often andmay
le
Hi Siddhartha,
On Sat, Feb 02 2019, Siddhartha Sen wrote:
> Hey Marting,
> I have disabled the boottrap and am able to bootstrap
> the compiler on my own. I have done as you said and have experimented a bit
> with gdb as well. I was facing trivial problems but nothing that the
Hello GCC,
My name is David Brown and I am interested in contributing to
libstdc++-v3. Specifically, I would like to begin implementing
https://wg21.link/p0355r7 having used its reference implementation in
several projects already.
I am aware that I will need to fill out some FSF forms for legal
Hi there,
I'd like to make handling of the __RTL function testcases where the
startwith pass name is either invalid, not used for that optimisation
level, or non-existant more understandable.
Currently a problem with the pass name leaves around state that causes
the compiler to ICE on other fu
Hi,
Suppose we have a program called foo which is built with gcc
-fprofile-generate, Now when foo is executed a bunch of .gcda files are
created.
What happens when foo is executed more than once. Are the .gcda files updated
with each execution? Or are the .gcda files overwritten with new
On February 19, 2019 5:19:11 PM GMT+01:00, Qing Zhao
wrote:
>Hi,
>
>Suppose we have a program called foo which is built with gcc
>-fprofile-generate, Now when foo is executed a bunch of .gcda files
>are created.
>
>What happens when foo is executed more than once. Are the .gcda files
>updated
I found a small spelling mistake in gcc source tree /gcc/config/gcn/gcn.c 5948
line,
output_operand_lossage ("invlaid fp constant");
“invlaid” sould be "invaild".
On Tue, 19 Feb 2019 at 17:49, xinxin wrote:
>
> I found a small spelling mistake in gcc source tree /gcc/config/gcn/gcn.c
> 5948 line,
>
>
> output_operand_lossage ("invlaid fp constant");
>
>
> “invlaid” sould be "invaild".
Thanks! Fixed by the attached patch, committed to trunk as obvious.
com
On Mon, Feb 18, 2019 at 01:13:31PM -0600, Peter Bergner wrote:
> I have a question about constraint usage in inline asm when we have
> an early clobber output operand. The test case is from PR89313 and
> looks like the code below (I'm using "r3" for the reg on ppc, but
> you could also use "rax" o
