Re: gcc-11-20210426 is now available

[Gerald Pfeifer]

On Mon, 26 Apr 2021, GCC Administrator via Gcc wrote:
> Snapshot gcc-11-20210426 is now available on
>   https://gcc.gnu.org/pub/gcc/snapshots/11-20210426/
> and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

Thanks for re-running the snapshot, Joseph, and updating 
the infrastructure (cf. 
https://gcc.gnu.org/pipermail/gcc/2021-April/235907.html)

To reduce potential confusion by users, I removed the bogus
11-20210425 snapshot from our download server.

Gerald

Links broken for C++ in web page "GCC online documentation: Latest releases"

[Pablo M. Ronchi via Gcc]

Dear GCC's documenters:

In the following page:

https://gcc.gnu.org/onlinedocs/
GCC online documentation

under the subheadings:

Latest releases
 GCC 11.1 manuals:

The following items have all their links broken (HTML,... tarball):

...
GCC 11.1 Standard C++ Library Manual (also in PDF or XML or an HTML tarball)
GCC 11.1 Standard C++ Library Reference Manual (also in PDF or XML GPL 
or XML GFDL or an HTML tarball)

...

The remaining items under "GCC 11.1 manuals" seem to be OK.

Thank you for your indispensable work

Regards

Pablo M. Ronchi

gcc-8-20210428 is now available

[GCC Administrator via Gcc]

Snapshot gcc-8-20210428 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/8-20210428/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 8 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-8 
revision 0d277114b4b2d0cb386c7abe409a81ca29d9d61d

You'll find:

 gcc-8-20210428.tar.xzComplete GCC

  SHA256=b220be4e95b6788b749e6c67cc20305b53b313ee29260ebdecaacd7b73619ca1
  SHA1=097a93d0f98f6c5177cdb81755f17223ee72fe65

Diffs from 8-20210422 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-8
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.

Could vector type of poly_int and compile-time constants be enabled at the same time ?

[JojoR via Gcc]

Hi,

I have a little know about for 'Sizes and offsets as runtime 
invariants’,

and need to add vector types like V2SImode as compile-time constants
with enabled vector types of runtime invariants.

Could I enable two vector types at same time ?
I guess it’s not allow :(

Could anyone give me some hints ?

Thanks,

Jojo R

GSoC Student Engagement

[Nick Vidal via Gcc]

Hello,

This is Nick Vidal from Rocket.Chat

We’ve been part of GSoC for 5 years now, and as a way to celebrate and
give back to the open source community, this year we are reaching out
to other GSoC organizations to provide assistance on setting up
Rocket.Chat to engage with students (pro bono).

Rocket.Chat is a leading open source chat platform, and we’ve been
using the platform itself to engage with our own GSoC students. With
Rocket.Chat, it’s possible to create private/public channels for each
student/project so that mentors and students can communicate, share
ideas, and keep track of progress both asynchronously and in real
time. It’s also possible to create integrations to display pull
requests, mergers, and issues directly on these channels.

Please let me know if you would be interested in trying Rocket.Chat to
engage with your GSoC students. Myself and the Community Engagement
team are at your full disposal to help. Our mission is to serve the
open source community!

Kind regards,
Nick

--
Rocket.Chat
https://rocket.chat

Re: State of AutoFDO in GCC

[Andi Kleen via Gcc]

On Mon, Apr 26, 2021 at 06:40:56PM +, Hongtao Yu wrote:
>Andi, thanks for pointing out the perf script issues. Can you please
>elaborate a bit on the exact issue you have seen? We’ve been using
>specific output of perf script such as mmap, LBR and callstack events
>filtered by process id. It works fine so far but may certainly hit issues
>in the future with extended uses.

Okay I took a look at the latest autofdo now. It seems to be basically
a LLVM project now that depends on LLVM to even build with all kinds
of dependency hell on some old LLVM version and other packages.

I guess gcc will really need a replacement that doesn't pull in
all of LLVM if it wants to continue supporting autofdo.

I'm myself unable to build now.

I'm using the old version I had a git fork of and that 
was before all of this. I added a patch to make it work
with the latest perf by ignoring increased perf_attr
and unknown perf events.

Honza please use

https://github.com/andikleen/autofdo -b perf-future

for testing.

-Andi

Is it very hard to support wasi backend?

[sotrdg sotrdg via Gcc]

I helped built libstdc++ on wasm32-wasi with clang. It works great.

However, are we going to have GCC’s own wasm32-wasi backend support in the 
future?

Sent from Mail for Windows 10