Snapshot gcc-13-20250117 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250117/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Friday, January 17th, 2025 at 5:44 AM, Mark Wielaard wrote:
>
>
> Hi Ihor,
>
> On Thu, Jan 16, 2025 at 08:44:54PM +, Ihor Solodrai via Gcc wrote:
>
> > An example of successful test run (you have to login to github to see
> > the logs):
> > h
Ihor Solodrai via Gcc writes:
> On Friday, January 17th, 2025 at 2:44 AM, Jose E. Marchesi
> wrote:
>
>> [...]
>>
>> > Ok. I disabled the execution of the test_progs-bpf_gcc test runner for now.
>> >
>> > I think we should check on the state of
On Fri, Jan 17, 2025 at 12:34 AM Cupertino Miranda
wrote:
>
> I remind that just as bad as the decl_tags it also misses a solution to
> the attribute ((preserve_access_index)).
> Something like #pragma clang push/pop is not viable in GCC.
>
> Jose proposed the p
t;
>
> Thank you. Sounds like a plan :)
>
> Is it possible to configure the CI to send an email to certain
> recipients when the build of the selftests with GCC fails? That would
> help us to keep an eye on the patches and either fix GCC or provide
> advise on how to fix the
Hi Ihor,
On Thu, Jan 16, 2025 at 08:44:54PM +, Ihor Solodrai via Gcc wrote:
> An example of successful test run (you have to login to github to see
> the logs):
> https://github.com/kernel-patches/bpf/actions/runs/12816136141/job/35736973856
>
> Currently 2513 of 4340 tests p
> On Thursday, January 16th, 2025 at 3:58 PM, Jose E. Marchesi
> wrote:
>
>>
>> [...]
>> > >
>> > > Effective BPF selftests denylist for GCC BPF is located here:
>> > > https://github.com/kernel-patches/vmtest/blob/master/ci/
I remind that just as bad as the decl_tags it also misses a solution to
the attribute ((preserve_access_index)).
Something like #pragma clang push/pop is not viable in GCC.
Jose proposed the patch in:
https://lore.kernel.org/bpf/20240503111836.25275-1-jose.march...@oracle.com/
Maybe you
On Thursday, January 16th, 2025 at 3:58 PM, Jose E. Marchesi
wrote:
>
> [...]
> > >
> > > Effective BPF selftests denylist for GCC BPF is located here:
> > > https://github.com/kernel-patches/vmtest/blob/master/ci/vmtest/configs/DENYLIST.test_progs-bpf_gcc
&g
> As of now, an important missing piece on GCC side is the decl_tags
> support, as they are heavily used by BPF selftests. See a message from
> Yonghong Song:
> https://gcc.gnu.org/pipermail/gcc-patches/2025-January/673841.html
Faust is working on a V2 of that patch series
Thank you for getting this up and running!
> Hi everyone.
>
> GCC BPF support in BPF CI has been landed.
>
> The BPF CI dashboard is here:
> https://github.com/kernel-patches/bpf/actions/workflows/test.yml
>
> A summary of what happens on CI (relevant to GCC BPF):
>
> On Thursday, January 16th, 2025 at 12:44 PM, Ihor Solodrai
> wrote:
>
>>
>>
>> Hi everyone.
>>
>> GCC BPF support in BPF CI has been landed.
>>
>> The BPF CI dashboard is here:
>> https://github.com/kernel-patches/bpf/actions/
Snapshot gcc-12-20250116 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250116/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Thursday, January 16th, 2025 at 12:44 PM, Ihor Solodrai
wrote:
>
>
> Hi everyone.
>
> GCC BPF support in BPF CI has been landed.
>
> The BPF CI dashboard is here:
> https://github.com/kernel-patches/bpf/actions/workflows/test.yml
>
> A summary of what happ
Wonderful news! Massive thanks for working on this.
> but if there are specific people who should be notified
> please let me know.
Please feel free to include me on that list too.
Hi everyone.
GCC BPF support in BPF CI has been landed.
The BPF CI dashboard is here:
https://github.com/kernel-patches/bpf/actions/workflows/test.yml
A summary of what happens on CI (relevant to GCC BPF):
* Linux Kernel is built on a target source revision
* Latest snapshots of GCC 15 and
Status
==
The GCC development branch which will become GCC 15 is now in
stage4, open for regression and documentation fixes only.
Quality Data
Priority # Change from last report
--- ---
P1 32 + 6
P2
Snapshot gcc-15-20250112 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250112/
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
Snapshot gcc-14-20250111 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250111/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20250110 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250110/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-12-20250109 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250109/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20250105 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20250105/
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
Snapshot gcc-14-20250104 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20250104/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> Hi everyone.
>
> I built and ran selftests/bpf with GCC 15-20241229, and would like to
> share my findings.
>
> Building required small adjustments in the Makefile, besides -std=gnu17
>
> With the following change we can mitigate int64_t issue:
>
> +pr
On Fri, Jan 3, 2025 at 3:48 PM Ihor Solodrai wrote:
>
> Hi everyone.
>
> I built and ran selftests/bpf with GCC 15-20241229, and would like to
> share my findings.
>
> Building required small adjustments in the Makefile, besides -std=gnu17
>
> With the following cha
Hi everyone.
I built and ran selftests/bpf with GCC 15-20241229, and would like to
share my findings.
Building required small adjustments in the Makefile, besides -std=gnu17
With the following change we can mitigate int64_t issue:
+progs/test_cls_redirect.c-CFLAGS := -nostdinc
+progs
Snapshot gcc-13-20250103 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20250103/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
, removing includes for these headers does not help the test in
> question, because some linux UAPI headers include libc headers when exported:
>
> In file included from /usr/include/netinet/udp.h:51,
> from progs/test_cls_redirect_dynptr.c:20:
>
If
> it doesn't... well, it is not the responsibility of the compiler to
> assure that. I will install a patch to switch to the wrapper stdint.h.
https://gcc.gnu.org/pipermail/gcc-patches/2025-January/672508.html
> On Fri, 2025-01-03 at 01:16 +0100, Jose E. Marchesi wrote:
>
> [...]
>
>> Yes, in the GCC BPF backend we are using
>>
>> use_gcc_stdint=provide
>>
>> which makes GCC to provide the version of stdint.h that assumes
>> freestand
On Fri, 2025-01-03 at 01:16 +0100, Jose E. Marchesi wrote:
[...]
> Yes, in the GCC BPF backend we are using
>
> use_gcc_stdint=provide
>
> which makes GCC to provide the version of stdint.h that assumes
> freestanding ("baremetal") mode. If we changed it to us
/usr/include/netinet/udp.h:51,
from progs/test_cls_redirect_dynptr.c:20:
/home/eddy/work/tmp/gccbpf/lib/gcc/bpf-unknown-none/15.0.0/include/stdint.h:43:24:
error: conflicting types for ‘int64_t’; have ‘long int’
43 | typedef __INT64_TYPE__ int64_t;
|
ude/x86_64-linux-gnu/bits/stdint-intn.h:27:19: error:
>> > conflicting types for ‘int64_t’; have ‘__int64_t’ {aka ‘long long int’}
>> >27 | typedef __int64_t int64_t;
>> > | ^~~
>> > In file included from progs/test_cls_redire
ing types for ‘int64_t’; have ‘__int64_t’ {aka ‘long long int’}
> >27 | typedef __int64_t int64_t;
> > | ^~~
> > In file included from progs/test_cls_redirect_dynptr.c:6:
> >
> > /ci/workspace/bpfgcc.20240922/lib/gcc/bpf-u
Snapshot gcc-12-20250102 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20250102/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
for ‘int64_t’; have ‘__int64_t’ {aka ‘long long
>> > int’}
>> > 27 | typedef __int64_t int64_t;
>> > | ^~~
>> > In file included from progs/test_cls_redirect_dynptr.c:6:
>> > /ci/workspace/bpfgcc.20240922/lib/gcc/bpf-unknown-none/15.0.0/include/stdint.h:4
int64_t;
> > | ^~~
> > In file included from progs/test_cls_redirect_dynptr.c:6:
> > /ci/workspace/bpfgcc.20240922/lib/gcc/bpf-unknown-none/15.0.0/include/stdint.h:43:24:
> > note: previous declaration of ‘int64_t’ with type ‘int64_t’ {aka ‘long
> > int’}
> > 43 |
^~~
> In file included from progs/test_cls_redirect_dynptr.c:6:
>
> /ci/workspace/bpfgcc.20240922/lib/gcc/bpf-unknown-none/15.0.0/include/stdint.h:43:24:
> note: previous declaration of ‘int64_t’ with type ‘int64_t’ {aka ‘long
> int’}
>43 | typedef __INT64_
23-compilant vmlinux.h. To conditionalize the declarations both the
> enum and typedef _Bool have to be matched, so it's actually two hacks.
> Although we do use hacks like this, noticed an interesting example
> today [1].
>
> Regardless of how the bool-related error is fixed (w
On Monday, December 30th, 2024 at 4:42 PM, Alexei Starovoitov
wrote:
>
>
> On Mon, Dec 30, 2024 at 12:59 PM Ihor Solodrai ihor.solod...@pm.me wrote:
>
> > On Monday, December 30th, 2024 at 12:36 PM, Sam James s...@gentoo.org wrote:
> >
> > > Andrew Pins
On Mon, Dec 30, 2024 at 12:59 PM Ihor Solodrai wrote:
>
> On Monday, December 30th, 2024 at 12:36 PM, Sam James wrote:
>
> >
> >
> > Andrew Pinski via Gcc gcc@gcc.gnu.org writes:
> >
> > > On Mon, Dec 30, 2024 at 12:11 PM Ihor Solodrai via Gcc gcc@gcc
Ihor Solodrai writes:
> On Monday, December 30th, 2024 at 12:36 PM, Sam James wrote:
>
>>
>
>>
>
>> Andrew Pinski via Gcc gcc@gcc.gnu.org writes:
>>
>
>> > On Mon, Dec 30, 2024 at 12:11 PM Ihor Solodrai via Gcc gcc@gcc.gnu.org
>> >
On Monday, December 30th, 2024 at 12:36 PM, Sam James wrote:
>
>
> Andrew Pinski via Gcc gcc@gcc.gnu.org writes:
>
> > On Mon, Dec 30, 2024 at 12:11 PM Ihor Solodrai via Gcc gcc@gcc.gnu.org
> > wrote:
> >
> > > Hello everyone.
> > >
> >
Andrew Pinski via Gcc writes:
> On Mon, Dec 30, 2024 at 12:11 PM Ihor Solodrai via Gcc
> wrote:
>>
>> Hello everyone.
>>
>> I picked up the work adding GCC BPF backend to BPF CI pipeline [1],
>> originally done by Cupertino Miranda [2].
>>
>>
On Mon, Dec 30, 2024 at 12:11 PM Ihor Solodrai via Gcc wrote:
>
> Hello everyone.
>
> I picked up the work adding GCC BPF backend to BPF CI pipeline [1],
> originally done by Cupertino Miranda [2].
>
> I encountered issues compiling BPF objects for selftests/bpf with
> rec
Hello everyone.
I picked up the work adding GCC BPF backend to BPF CI pipeline [1],
originally done by Cupertino Miranda [2].
I encountered issues compiling BPF objects for selftests/bpf with
recent GCC 15 snapshots. An additional test runner binary is supposed
to be generated by tools/testing
On Mon, Dec 30, 2024 at 11:16:37AM +1100, raf wrote:
> Rather than expecting all C compilers to be modified to
> ignore the #! line, it should be possible to configure
> /bin/sh to do the desired thing. If a file is
> executable and has no #! line, the kernel will execute
> it via /bin/sh. Anyone
f
On Sun, Dec 29, 2024 at 01:08:48PM -0600, Paul Markfort via Gcc
wrote:
>
> You can also do what I do now (the example in my first message), and don't
> need to pre-process the file before sending it to the compiler. What
> Jonothan suggested ("Still it would be a nice
Snapshot gcc-15-20241229 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20241229/
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
uot;#end" (or some other token).
Basically "#!" would become a special comment (but would only work if the file
essentially started with it - first non-blank characters).
Think of users who use scripts all the time, but rarely use Compiled languages.
On 2024-12-28 4:47 PM, Flo
>>> cat e
#!/bin/sh
#
#
root -l -b <
int main(void)
{
puts("Hello, world, you can ignore all that particle physics if you like.");
printf("By the way, log(2025) is %lf\n",log(2025.));
printf("Here I have suppressed the banner\n");
return 0;
}
DOIT
>>> ./e
Hello, world, you can ignore al
On Sat, Dec 28, 2024 at 2:48 PM Florian Weimer wrote:
> [...]
>
>
> Still it would be a nice touch if we could do
>
> #!/usr/bin/gcc -f
> #include
> int main()
> {
> puts("Hello, world");
> return 0;
> }
>
re previously mentioned "roo
* Jonathan Wakely via Gcc:
> Here's a complete example:
>
> #!/bin/sh
> set -e
> out=$(mktemp /tmp/a.out.XX)
> sed 1,5d "$0" | gcc -x c - -o "$out"
> exec "$out"
>
> #include
> int main()
> {
> puts("Hello, worl
Snapshot gcc-14-20241228 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20241228/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> > But why would you want to install another program, if you could
> > essentially use the tools you already have.
> >
> > I think gcc (and all the compilers) should support the "#!" in source
> > files to make something similar easily possible.
>
>
> I agree w
On Sat, 28 Dec 2024, 16:17 Jonathan Wakely, wrote:
>
>
> On Sat, 28 Dec 2024, 15:26 Paul Smith via Gcc, wrote:
>
>> On Sat, 2024-12-28 at 09:00 -0600, Paul Markfort via Gcc wrote:
>> > I realize that C is not a line oriented language and usually
>> >
On Sat, 28 Dec 2024, 15:26 Paul Smith via Gcc, wrote:
> On Sat, 2024-12-28 at 09:00 -0600, Paul Markfort via Gcc wrote:
> > I realize that C is not a line oriented language and usually
> > completely ignores line termination characters (so yes this is
> > probably not
On Sat, 2024-12-28 at 09:00 -0600, Paul Markfort via Gcc wrote:
> I realize that C is not a line oriented language and usually
> completely ignores line termination characters (so yes this is
> probably not a simple thing to do).
You probably really want this capability added to the pre
learned
that most people use open source, but a very very small percentage actually
contribute to it. So basically if it is a great idea, go make it happen!
Note I have not done the python interpreter for C/C++
On Sat, Dec 28, 2024 at 10:01 AM Paul Markfort via Gcc
wrote:
> To be clear.
&g
To be clear.
I am not suggesting that Compilers like GCC be modified to act on the "#!", or
even fully support it.
Just that they be simply modified to ignore "#!" - on the first line (which should terminate with
either a "/r" or "/n").
This allows t
for
> this purpose.
> But why would you want to install another program, if you could
> essentially use the tools you already have.
>
> I think gcc (and all the compilers) should support the "#!" in source
> files to make something similar easily possible.
I ag
Snapshot gcc-13-20241227 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20241227/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-12-20241226 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20241226/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
program, if you could essentially use
the tools you already have.
I think gcc (and all the compilers) should support the "#!" in source files to
make something similar easily possible.
So one could write C or C++ (or Fortran, etc) code and just run the source file
to compile and run.
The B
Snapshot gcc-15-20241222 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20241222/
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
Snapshot gcc-14-20241221 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20241221/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20241220 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20241220/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-12-20241219 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20241219/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20241215 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20241215/
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
Snapshot gcc-14-20241214 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20241214/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20241213 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20241213/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-12-20241212 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20241212/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-15-20241208 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/15-20241208/
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
Snapshot gcc-14-20241207 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20241207/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-13-20241206 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20241206/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Snapshot gcc-12-20241205 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20241205/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
"James K. Lowden" writes:
Hello James,
> I went to https://pretalx.fosdem.org/fosdem-2025/cfp today. It says
> the deadline isn't the 15th, but was yesterday! Am i really too
> late?
Dec 15th is for the schedule announcement: we have ~15 days to read all
the proposals and decide which one we
Hi James!
On 2024-12-01T17:34:13-0500, "James K. Lowden" wrote:
> On Tue, 01 Oct 2024 11:48:34 +0200
> Thomas Schwinge wrote:
>
>> I need two, three people as co-organizers:
>> for evaluating submissions (before 2024-12-15),
>
> I went to https://pretalx.fosdem.org/fosdem-2025/cfp today. It sa
On Tue, 01 Oct 2024 11:48:34 +0200
Thomas Schwinge wrote:
> I need two, three people as co-organizers:
> for evaluating submissions (before 2024-12-15),
Hi Thomas,
I went to https://pretalx.fosdem.org/fosdem-2025/cfp today. It says
the deadline isn't the 15th, but was yesterday! Am i reall
Hi Gerald,
On Mon, Dec 02, 2024 at 12:13:35AM +0100, Gerald Pfeifer wrote:
> 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!
Hi Bradley,
Thanks for following the discussion and your input.
We have also been discussing some policy wording changes on gcc-patches:
https://inbox.sourceware.org/gcc-patches/20241202101600.1041524-1-m...@klomp.org/T
If you have any suggestions for improving the actual wording change
that
the correct invocation is:
>
> $ git push origin --delete python-formatting
>
> against your local repo where your origin is
> ssh://ger...@gcc.gnu.org/git/gcc-wwwdocs.git
>
> If that doesn't work we'll have to clean it up on the server.
I believe things are fine?
%
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
drop that branch again from the main gcc.gnu.org repo?
I believe the correct invocation is:
$ git push origin --delete python-formatting
against your local repo where your origin is
ssh://ger...@gcc.gnu.org/git/gcc-wwwdocs.git
If that doesn't work we'll have to clean it up on the server.
Cheers,
Mark
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
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
Lynch Jr. via Gcc,
> wrote:
> > Is it possible to build gcc 13 with gcc 14 ?
>
> Yes
>
> >
> > My system updated to gcc 14 and I am doing some private development
> > for
> > hardware stesting of a new memory addressing paradigm using the GCC
> > 1
Snapshot gcc-14-20241130 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20241130/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Sat, 30 Nov 2024 at 10:10, Jakub Jelinek wrote:
>
> On Sat, Nov 30, 2024 at 09:54:02AM +, Jonathan Wakely via Gcc wrote:
> > On Sat, 30 Nov 2024, 09:01 David H. Lynch Jr. via Gcc,
> > wrote:
> >
> > > Is it possible to build gcc 13 with gcc 14 ?
> >
On Nov 30 2024, Jakub Jelinek via Gcc wrote:
> Note, there are some exceptions, I think e.g. Ada needs the same or older
> major version of gnat and doesn't work well with newer Ada (but if you don't
> need Ada, that is a non-issue).
That may also be an issue for D.
--
On Sat, Nov 30, 2024 at 09:54:02AM +, Jonathan Wakely via Gcc wrote:
> On Sat, 30 Nov 2024, 09:01 David H. Lynch Jr. via Gcc,
> wrote:
>
> > Is it possible to build gcc 13 with gcc 14 ?
> >
>
> Yes
Note, there are some exceptions, I think e.g. Ada needs the sam
On Sat, 30 Nov 2024, 09:54 Jonathan Wakely, wrote:
>
>
> On Sat, 30 Nov 2024, 09:01 David H. Lynch Jr. via Gcc,
> wrote:
>
>> Is it possible to build gcc 13 with gcc 14 ?
>>
>
> Yes
>
>
>> My system updated to gcc 14 and I am doing some private
On Sat, 30 Nov 2024, 09:01 David H. Lynch Jr. via Gcc,
wrote:
> Is it possible to build gcc 13 with gcc 14 ?
>
Yes
> My system updated to gcc 14 and I am doing some private development for
> hardware stesting of a new memory addressing paradigm using the GCC 13
> code base
Is it possible to build gcc 13 with gcc 14 ?
My system updated to gcc 14 and I am doing some private development for
hardware stesting of a new memory addressing paradigm using the GCC 13
code base.
Now I can't compile.
Do I need to revert my base compiler to gcc 13 ?
> On 11/24/24 11:49 AM, Bradley M. Kuhn wrote:
> > One size doesn't necessarily fit all. Perhaps if you're changing the DCO
> > text for the toolchain projects at this moment, it might be a good time to
> > consider if the Linux DCO text suits your project perfectly.
Carlos O'Donell wrote:
> This
Snapshot gcc-13-20241129 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20241129/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On 11/24/24 11:49 AM, Bradley M. Kuhn wrote:
> One size doesn't necessarily fit all. Perhaps if you're changing the DCO
> text for the toolchain projects at this moment, it might be a good time to
> consider if the Linux DCO text suits your project perfectly.
This is not a change of the DCO text.
Snapshot gcc-12-20241128 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20241128/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On 28/11/2024 12:18, Aaron Peter Bachmann via Gcc wrote:
Two suggestions for GCC beginners projects
I watched some of the 2024 Gnu Cauldron videos. The question of what
could be a suitable project for a beginner came up. I have two suggestions:
1. Add a warning when users use reserved or
Two suggestions for GCC beginners projects
I watched some of the 2024 Gnu Cauldron videos. The question of what
could be a suitable project for a beginner came up. I have two suggestions:
1. Add a warning when users use reserved or potentially reserved
identifiers in their code. This
1 - 100 of 21222 matches
Mail list logo
