On 2024-09-17 01:17, Jonathan Wakely via Gcc wrote:
On Mon, 16 Sept 2024, 23:40 Alain Mosnier, wrote:
On 2024-09-16 23:54, Alain Mosnier wrote:
On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote:
When a particular snapshot is ready for public consumption the
LATEST-15
link is update
On Mon, 16 Sept 2024, 23:40 Alain Mosnier, wrote:
> On 2024-09-16 23:54, Alain Mosnier wrote:
> > On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote:
> >
> > > When a particular snapshot is ready for public consumption the
> > LATEST-15
> > > link is updated
> >
> > I'm new here. Where do I
On 2024-09-16 23:54, Alain Mosnier wrote:
On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote:
> When a particular snapshot is ready for public consumption the
LATEST-15
> link is updated
I'm new here. Where do I find the LATEST-15 link? Can I "safely" use
the snapshot after the email I
On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote:
> When a particular snapshot is ready for public consumption the LATEST-15
> link is updated
I'm new here. Where do I find the LATEST-15 link? Can I "safely" use the
snapshot after the email I am replying to has been sent?
Thanks in ad
Thank you for the BZ link. Actually my problem was configuring GCC build
with
--with-build-config=bootstrap-lto and --enable-lto. I'm researching
compiler theory (reading the Dragon book now) and I would like to contribute
to our
lovely compiler(s), specially gfortran.
On Mon, Sep 16, 2024 at 10:0
On Sun, 2024-09-15 at 15:20 +0330, Ghorban M. Tavakoly via Gcc wrote:
> Hi
>
> On Sun, Sep 15, 2024 at 11:59 AM Jan Hubicka wrote:
>
> > > On Sat, Sep 14, 2024 at 1:17 PM Ghorban M. Tavakoly via Gcc
> > > wrote:
> > > >
> > > > > > Is there any change to have some LTO progress indicator
> > >
> Am 16.09.2024 um 14:45 schrieb Jonathan Wakely :
>
> On Mon, 16 Sept 2024 at 13:13, Richard Biener
> wrote:
>>
>>> On Mon, Sep 16, 2024 at 1:37 PM Jonathan Wakely via Gcc
>>> wrote:
>>>
>>> Git supports signing commits with a GPG key, and more recently (since
>>> Git 2.34) also started
> On Sep 16, 2024, at 8:13 AM, Richard Biener via Gcc wrote:
>
> On Mon, Sep 16, 2024 at 1:37 PM Jonathan Wakely via Gcc
> wrote:
>>
>> Git supports signing commits with a GPG key, and more recently (since
>> Git 2.34) also started supporting signing with an SSH key. The latter
>> is IMHO m
On Mon, Sep 16, 2024 at 9:40 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> - Am 16. Sep 2024 um 15:24 schrieb David Edelsohn dje@gmail.com:
>
> > On Mon, Sep 16, 2024 at 9:15 AM Sebastian Huber <
> > sebastian.hu...@embedded-brains.de> wrote:
> >
> >> - Am 16. S
- Am 16. Sep 2024 um 15:24 schrieb David Edelsohn dje@gmail.com:
> On Mon, Sep 16, 2024 at 9:15 AM Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
>
>> - Am 16. Sep 2024 um 15:02 schrieb David Edelsohn dje@gmail.com:
>>
>> > On Sun, Sep 15, 2024 at 7:29 PM Sebast
On Mon, Sep 16, 2024 at 9:15 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> - Am 16. Sep 2024 um 15:02 schrieb David Edelsohn dje@gmail.com:
>
> > On Sun, Sep 15, 2024 at 7:29 PM Sebastian Huber <
> > sebastian.hu...@embedded-brains.de> wrote:
> >
> >> Hello,
> >>
> >> t
- Am 16. Sep 2024 um 15:02 schrieb David Edelsohn dje@gmail.com:
> On Sun, Sep 15, 2024 at 7:29 PM Sebastian Huber <
> sebastian.hu...@embedded-brains.de> wrote:
>
>> Hello,
>>
>> the PowerPC SPE port was obsoleted in GCC 8. It was moved from the general
>> PowerPC directory (gcc/config/r
On Sun, Sep 15, 2024 at 7:29 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello,
>
> the PowerPC SPE port was obsoleted in GCC 8. It was moved from the general
> PowerPC directory (gcc/config/rs6000) to a separate directory
> (gcc/config/powerpcspe). In GCC 9, it was removed d
On Mon, 16 Sept 2024 at 13:13, Richard Biener
wrote:
>
> On Mon, Sep 16, 2024 at 1:37 PM Jonathan Wakely via Gcc
> wrote:
> >
> > Git supports signing commits with a GPG key, and more recently (since
> > Git 2.34) also started supporting signing with an SSH key. The latter
> > is IMHO much easie
On Mon, Sep 16, 2024 at 1:37 PM Jonathan Wakely via Gcc wrote:
>
> Git supports signing commits with a GPG key, and more recently (since
> Git 2.34) also started supporting signing with an SSH key. The latter
> is IMHO much easier to set up, because anybody who can push to the GCC
> repo already h
Git supports signing commits with a GPG key, and more recently (since
Git 2.34) also started supporting signing with an SSH key. The latter
is IMHO much easier to set up, because anybody who can push to the GCC
repo already has an SSH key configured.
To start signing your git commits, just enable
Dear Gcc,
I'm checking if you're interested in acquiring the Members/Distribution list
· New Mexico Chamber of Commerce 2024 (New Mexico, USA)
·1,000+ Contacts
I’m waiting for your response so i can let you know the price & more
information.
Regards,
Matilda – Busi
As a reminder, I added .b4-config to the top-level, so that using the
kernel's b4 tool inside a GCC source tree will automatically use
inbox.sourceware.org and will submit mail to gcc-patc...@gcc.gnu.org
See https://b4.docs.kernel.org/en/latest/ for docs on how to use b4 to
work with patches in th
I've pushed .editorconfig files for the libstdc++-v3 sub-directory:
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663071.html
As mentioned there, I'll experiment with similar files for the rest of
the tree. I will share those files and it would be helpful if people
who work on the rest
* Jason Merrill via Gcc:
> We moved to a bootstrap requirement of C++11 in GCC 11, 8 years after
> support was stable in GCC 4.8.
Note that some documentation still says C++03, for example:
| The directories gcc, libcpp and fixincludes may use C++03. They may
| also use the long long type if the
20 matches
Mail list logo
