config/dfp.m4 license?

[Christophe Lyon via Gcc]

Hi!

The config/dfp.m4 file does not have a license header. Several other .m4 
files in the same directory have a GPL header, many others do not.


Can someone confirm the license of dfp.m4 and add the missing header if 
applicable?


Thanks!

Christophe

Re: config/dfp.m4 license?

[Andrew Pinski via Gcc]

On Fri, Apr 29, 2022 at 1:45 AM Christophe Lyon via Gcc  wrote:
>
> Hi!
>
> The config/dfp.m4 file does not have a license header. Several other .m4
> files in the same directory have a GPL header, many others do not.
>
> Can someone confirm the license of dfp.m4 and add the missing header if
> applicable?

The history is that the code was taken from gcc/configure.ac so yes it
should be the same as that.


>
> Thanks!
>
> Christophe

Re: GCC 12.0.1 Status Report (2022-04-28)

[LIU Hao via Gcc]

在 2022-04-28 22:59, Jakub Jelinek via Gcc 写道:

Status
==

We have reached zero P1 regressions today and releases/gcc-12 branch has
been created.  GCC 12.1-rc1 will be built likely tomorrow.
The branch is now frozen for blocking regressions and documentation
fixes only, all changes to the branch require a RM approval now.

If no show stoppers appear, we'd like to release 12.1 late next week,
or soon after that, if any important issues are discovered and
fixed, rc2 could be released next week.




Congrats. I have so far bootstrapped GCC 12.0 on {x86_64,i686}-w64-mingw32 and 
seen no problems.



--
Best regards,
LIU Hao


OpenPGP_signature
Description: OpenPGP digital signature

Re: FW: ompd_get_thread_id in OMPD implementation

[Jakub Jelinek via Gcc]

On Sat, Apr 09, 2022 at 12:38:11AM +0200, Ahmed Sayed Mousse wrote:
> Sorry for the late reply.
> I did check gomp_thread_self but I'm still not sure about what I should do,
> maybe because I lack experience/knowledge.
> Here is where my thinking is going right now and I hope you tell me if I'm
> wrong.

Sorry for the delay, I've been busy with GCC 12.

> in gomp_thread_to_pthread_t there are 4 possible outputs
> 1 - if LIBGOMP_USE_PTHREADS is enabled
>  {
> first  pthread_self() if the thread calling is the same thread as the
> function input.
> or  gomp_thread->handle in case GOMP_NEEDS_THREAD_HANDLE is enabled.
> or  pthread_self () + ((uintptr_t) input_thread - (uintptr_t)
> calling_thread)
> }

ompd_get_thread_id is for mapping of the OMPD thread id to the native
thread id.  If LIBGOMP_USE_PTHREADS, we are using POSIX threads, so
OMPD_THREAD_ID_PTHREAD is what we want to provide.
If GOMP_NEEDS_THREAD_HANDLE, then we want to read the handle member for
it and return it.  Otherwise as the comment says, we optimize and
because we know that in the initial-exec TLS model &gomp_tls_data - 
pthread_self ()
is the same for each thread, we don't store the handle at all, so
ompd_get_thread_id instead needs to compute the bias.
If it is too hard to do it in libgompd.so alone, perhaps during
gompd_load libgomp.so.1 could compute it and store in some variable
that libgompd.so can then read.

> 2 -if LIBGOMP_USE_PTHREADS not enabled
> - empty struct casted to a pthread_t
> currently think i should check for the GOMP_NEED_THREAD_HANDLE, if it's
> enabled i extract the pthread_t  from the gomp_thread handle given in the
> function and return that.
> If it's not enabled then I return an empty struct or an rc_unspported
> return code.
> Note:
> The openmp specification doesn't really tell me how things should be
> done so I get confused a lot and I think I have a misunderstanding of the
> function.
>  I would appreciate it a lot if I get any directions to where I can
> increase my knowledge around this part.

If LIBGOMP_USE_PTHREADS is not enabled, then it is libgomp.a built for one
of the offloading targets, either NVPTX or GCN.  We then can't return
OMPD_THREAD_ID_PTHREAD, threads are numbered differently there, they are
either the CUDA threads or GCN threads.  But I think at least initially
we only build libgompd.so for the host so how exactly we OMPD offloading
should be postponed until after the host handling works.

Jakub

GCC 12.1 Release Candidate available from gcc.gnu.org

[Jakub Jelinek via Gcc]

The first release candidate for GCC 12.1 is available from

 https://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/
 ftp://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/

and shortly its mirrors.  It has been generated from git commit
r12-8321-g621650f64fb667.

I have so far bootstrapped and tested the release candidate on
x86_64-linux.  Please test it and report any issues to bugzilla.

If all goes well, I'd like to release 12.1 on Friday, May 6th.

[gen-16862] Invitation to the CERT Vendor Meeting 2022 (June 6)

[cert+donotreply--- via Gcc]

While it's unusual for us to hold meetings so close together, it's been an 
unusual couple of years, and we are holding a full day, hybrid event on June 6 
2022, the Monday of RSAC 2022. The meeting will be held from 9 AM to 5 PM PDT, 
in person at the Marriott Marquis in San Francisco, CA, US, and online via Zoom 
Webinar.

Register here: 

Registration options include in-person, virtual, or both.

Questions/issues about registration, logistics, etc: 

Topical discussion: 

We actively seek ideas for topics that are of interest to you, and we welcome 
those wishing to speak or lead a discussion topic or participate on a panel. 
The draft/working list topics includes:

 * UEFI vulnerability analysis

 * Linux Vendor Firmware Service (LVFS), possibly connected to the UEFI topic, 
probably also with supply chain/SBOM implications

 * A CVD protocol

 * CVE

 * SBOM, VEX

 * Government regulations impacting CVD

While we're more or less happy to decide the agenda ourselves, we'd be happier 
with your input, and you might be too.

Regards,

 - Art




This e-mail was sent to you as a user of our VINCE service, in accordance with 
our privacy policy. Please advise us if you believe you have received this 
e-mail in error.

gcc-11-20220429 is now available

[GCC Administrator via Gcc]

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

This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch 
releases/gcc-11 revision 14aad65778c64eb62fd4055c0986af2f6e54f97b

You'll find:

 gcc-11-20220429.tar.xz   Complete GCC

  SHA256=d916b04b3b1e3ab67960967f6d49da64af76e43a04d0c66374bb1dfa694b5829
  SHA1=ce6e54b719d8944f3efac6acebd848b665fe0905

Diffs from 11-20220423 are available in the diffs/ subdirectory.

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

How to regenerate aclocal.m4?

[Zopolis0 via Gcc]

I'm trying to regenerate autotools files in liboffloadmic (and other
directories) but when running automake it tells me I need to run aclocal,
which gives me a warning about not finding AM_ENABLE_MULTILIB in library,
which then translates into an autoconf error. How do I fix this? Is there a
specific aclocal version?