[no subject]

2024-08-18 Thread sudo yuwc via Gcc
สวัสดีครับ ขออนุญาตแนะนำ
✔️ทุนหมุนเวียนระยะสั้น ดอกเบี้้ยถูก
✔️อนุมัติสูงสุด 5,000,000 บาท
✔️ไม่เช็คเครดิต บูโร  ไม่ต้องมีบุคคลค้ำประกัน
✔️อัตราดอกเบี้ยต่ำ ลดต้น ลดดอกเบี้ย
✔️ถ้าท่านสนใจบริการของเรา โทรด่วนหาเรา
☎️ 082-5928519 คุณเอก
Line ID : esc.credit
(ให้เราเป็นส่วนหนึ่งในครอบครับท่านนะครับ)


Re: Simple GCC projects page

2024-08-18 Thread Gerald Pfeifer
On Tue, 20 Mar 2018, Christopher Higgs via gcc wrote:
> If this belongs in a different mailbox, please let me know where it 
> should be sent.

This was the right address, though sadly it somehow fell through the 
cracks originally.

> I would like to start contributing to GCC. In viewing the relevant pages 
> it became clear that they have not been updated for some time, which 
> makes starting to contribute a bit more challenging.
> 
> To name a few on the Simple GCC projects page:1. A few references are 
> made to the java front-end.

Indeed, and this is something we (specifically Eric) addressed, together 
with various other issues on this page.

> Under code cleanliness, the bullet for enormous files lists files in the 
> 150-500K sizes. These sizes are not current and there are at least a 
> couple of files in the MB range (the C++ parser.c file for example).

Eric updated these as well, alas some have further grown; I'll see to do a 
new tally and update that.

> Simplifying parser action code. GCC seems to have migrated away from 
> parser generators in favor of ad hoc approaches. Does this project still 
> apply?

I don't think so, and will push a patch to remove this and associated 
items in a minute.

A belated thank you for your feedback; I'll be looking for further issue 
and will happily look into anything else you may find.

Gerald


Re: smtgcc translation validation

2024-08-18 Thread Gerald Pfeifer
On Sat, 30 Sep 2023, Krister Walfridsson via Gcc wrote:
> I have now released the new implementation for translation validation I talked
> about at the GNU Tools Cauldron last week:
>   https://github.com/kristerw/smtgcc

Wouldn't it be appropriate/nice to promote this a bit more strongly from 
gcc.gnu.org?

One example I can think of is https://gcc.gnu.org/extensions.html .

Another might be https://gcc.gnu.org/bugs/ to help understand whether 
something is a user bug or GCC bug?

Happy to accept patches, or if you want to suggest some text massage that 
into HTML and add it.

Gerald


gcc-15-20240818 is now available

2024-08-18 Thread GCC Administrator via Gcc
Snapshot gcc-15-20240818 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/15-20240818/
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 master 
revision fc41263061808a8539ba7ee1f607920a54e7b265

You'll find:

 gcc-15-20240818.tar.xz   Complete GCC

  SHA256=02a7a8de5d83079d1fe11c75a5d03e01f32a937917e1c15aa95f94cb54573aae
  SHA1=9d11c00b34e868e2e42bdd5a8a6dc5c09377dfc4

Diffs from 15-20240811 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-15
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.


Re: Simple GCC projects page

2024-08-18 Thread Eric Gallager via Gcc
On Sun, Aug 18, 2024 at 8:21 AM Gerald Pfeifer  wrote:
>
> On Tue, 20 Mar 2018, Christopher Higgs via gcc wrote:
> > If this belongs in a different mailbox, please let me know where it
> > should be sent.
>
> This was the right address, though sadly it somehow fell through the
> cracks originally.
>
> > I would like to start contributing to GCC. In viewing the relevant pages
> > it became clear that they have not been updated for some time, which
> > makes starting to contribute a bit more challenging.
> >
> > To name a few on the Simple GCC projects page:1. A few references are
> > made to the java front-end.
>
> Indeed, and this is something we (specifically Eric) addressed, together
> with various other issues on this page.
>
> > Under code cleanliness, the bullet for enormous files lists files in the
> > 150-500K sizes. These sizes are not current and there are at least a
> > couple of files in the MB range (the C++ parser.c file for example).
>
> Eric updated these as well, alas some have further grown; I'll see to do a
> new tally and update that.
>
> > Simplifying parser action code. GCC seems to have migrated away from
> > parser generators in favor of ad hoc approaches. Does this project still
> > apply?
>
> I don't think so, and will push a patch to remove this and associated
> items in a minute.
>
> A belated thank you for your feedback; I'll be looking for further issue
> and will happily look into anything else you may find.
>

Oh yeah, I remember there being a few other projects on there that I
also remember feeling unsure about how relevant they still were;
definitely let us know if you find anything else that seems
outdated...

> Gerald