Thanks.
I am only building C/C++ not the rest of the suite.
Most of my changes so far are to the c/c++ parser. But I will have
changes to the code generation backends.
I was having a problem with building my code - late in the build
process - I beleive when it was getting ready to run unit t
On Sun, 1 Dec 2024, Gerald Pfeifer wrote:
> I tried to delete it via
>
> # git push origin --delete remotes/origin/python-formatting
>
> alas just get
>
> error: unable to delete 'remotes/origin/python-formatting': remote ref does
> not exist
>
> Any idea how to drop that branch again f
Snapshot gcc-15-20241201 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20241201/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 15 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Some modern CPU's now have control flow enforcement. Here's how it
works on Intel CPU's:
"The shadow stack stores a copy of the return address of each CALL. On
a RET, the processor checks if the return address stored in the normal
stack and shadow stack are equal. If the addresses are not equal, t
On Sun, 1 Dec 2024, Alexander Monakov wrote:
> You have to use the name of the branch in the remote repo,
> "python-formatting":
>
> git push --delete origin python-formatting
That did the job, thank you!
On Sun, 1 Dec 2024, Mark Wielaard wrote:
> I believe the correct invocation is:
>
> $ g
Hi,
I had a discussion about this with another WG14 member when this was
voted in. We both voted against, because this is nefarious for static
analysis.
However, I think this can be though to resemble how 'const' works in the
standard:
const char cbuf[10];
memcpy((char *)cbuf,
> > And get clarified the qsort/bsearch cases whether it is about just
> > nmemb == 0 or nmemb * size == 0.
>
> C does not support zero-sized objects, so that's something for us to
> figure out on our own. We can treat size == 0 as invalid because the
> functions can't work, as they use pointers
Hi Gerald,
On Sun, Dec 01, 2024 at 07:26:45PM +0100, Gerald Pfeifer wrote:
> On Fri, 23 Aug 2024, Eric Gallager wrote:
> >>> The branch, python-formatting has been created
> >>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit)
> >> Hmm, are you intentionally creating a branch for the
On Fri, 23 Aug 2024, Eric Gallager wrote:
>>> The branch, python-formatting has been created
>>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit)
>> Hmm, are you intentionally creating a branch for the wwwdocs repository
>> (i.e., our web pages)? I don't recall us having used one befor
