On 2/16/23 08:57, Richard Biener wrote:
On Wed, Feb 15, 2023 at 11:31 PM Andrew MacLeod via Gcc wrote:
On 2/15/23 14:50, Andrew Pinski wrote:
Hi,
While fixing PR 108354, I came across that
ssa_name_has_boolean_range calls get_range_query with cfun as the
argument but sometimes while i
Hi!
The following is not an actual problem for me or GCC/Rust; just for your
information:
I've just pushed to GCC devel/rust/master branch
Git commits cc23831ec66..74913f718b0, which 'hooks/post_receive.py' threw
up upon:
$ git push upstream github/Rust-GCC/gccrs/master:devel/rust/master
On 2/16/23 13:26, Thomas Schwinge wrote:
> Hi!
>
> The following is not an actual problem for me or GCC/Rust; just for your
> information:
Hello.
Thanks for letting me know.
>
> I've just pushed to GCC devel/rust/master branch
> Git commits cc23831ec66..74913f718b0, which 'hooks/post_receive.p
Hi!
I was preparing an example program of a use-after-realloc bug,
when I found that GCC doesn't warn in a case where it should.
alx@debian:~/tmp$ cat realloc.c
#include
#include
#include
#include
#include
static inline char *
xstrdup(const char *s)
{
char *p;
p = strdup(
On Thu, 2023-02-16 at 15:35 +0100, Alejandro Colomar via Gcc wrote:
> Hi!
>
> I was preparing an example program of a use-after-realloc bug,
> when I found that GCC doesn't warn in a case where it should.
>
>
> alx@debian:~/tmp$ cat realloc.c
> #include
> #include
> #include
> #include
> #in
Hello GCC community.
After spending last decade (including my diploma thesis even more)
of my life working on GCC, I decided to leave the project and try
a different job. I would like to thank all the community members I had
change to interact with, I learned so much and enjoyed the journey!
I'll
Hi Martin,
On Thu, 2023-02-16 at 16:54 +0100, Martin Liška wrote:
> After spending last decade (including my diploma thesis even more)
> of my life working on GCC, I decided to leave the project and try
> a different job. I would like to thank all the community members I had
> change to interact w
On Thu, Feb 16, 2023 at 10:54 AM Martin Liška wrote:
> Hello GCC community.
>
> After spending last decade (including my diploma thesis even more)
> of my life working on GCC, I decided to leave the project and try
> a different job. I would like to thank all the community members I had
> change
On Thu, 16 Feb 2023, Martin Liška wrote:
> Well, the https://github.com/AdaCore/git-hooks were ported to Python 3
> some time ago and I thought we've been using the updated version. But it
> seems we're still on python2.7 :((
>
> Joseph, can we update it, please?
If someone wishes to update th
Martin,
> Hello GCC community.
>
> After spending last decade (including my diploma thesis even more)
> of my life working on GCC, I decided to leave the project and try
> a different job. I would like to thank all the community members I had
> change to interact with, I learned so much and enjoye
Snapshot gcc-10-20230216 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20230216/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
[CC: Added those who contributed to the discussion in linux-man@,
and also the authors of N2861 for C2x]
Hi David,
On 2/16/23 16:15, David Malcolm wrote:
> On Thu, 2023-02-16 at 15:35 +0100, Alejandro Colomar via Gcc wrote:
>> Hi!
>>
>> I was preparing an example program of a use-after-reall
On 2/17/23 02:04, Alejandro Colomar wrote:
> [CC: Added those who contributed to the discussion in linux-man@,
> and also the authors of N2861 for C2x]
[...]
>
> There was a discussion in linux-man@ some years ago, which now I realize it
> didn't end up being applied (I thought we had appli
On Tue, 14 Feb 2023, NightStrike wrote:
>> Alas http://www.wlandry.net/Projects/FTensor has been down for a while,
>> and there does not appear to be a new location?
> https://wlandry.net/Projects/FTensor/ works
Ah, indeed. Thank you! Somehow that must have been the one combination I
did not try.
> On 17 Feb 2023, at 01:05, Alejandro Colomar via Gcc wrote:
>
> On 2/17/23 02:04, Alejandro Colomar wrote:
>> [CC: Added those who contributed to the discussion in linux-man@,
>> and also the authors of N2861 for C2x]
>
> [...]
>
>>
>> There was a discussion in linux-man@ some years ago
On 2023-02-16 10:15, David Malcolm via Gcc wrote:
I'm not convinced that it's useful to the end-user to warn about the
"use of q itself" case.
FWIW, -Wuse-after-free=3 already should do this:
At level 3, the warning also diagnoses uses of indeterminate pointers in
equality expressions. All u
16 matches
Mail list logo
