gcc-13-20230219 is now available

[GCC Administrator via Gcc]

Snapshot gcc-13-20230219 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/13-20230219/
and on various mirrors, see http://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 master 
revision b9c83e7789f7eec9871e370739baa55fd70be4cf

You'll find:

 gcc-13-20230219.tar.xz   Complete GCC

  SHA256=b10e0e0ad66cc64f4e7ec2150a220bea05c61dc2ceeef8cffd86deb32c59f764
  SHA1=b378b1a47cb54c7a4da57d767f541ac6561a1d4b

Diffs from 13-20230212 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-13
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: GSOC 2023 Contribution Request

[Ankur Saini via Gcc]

Hi,

I am neither the org-admin for GSoC, nor a mentor for any of the
proposed projects. Just a community member like you.

Here are a few things you can do till the time you get a response from
either of those:

- Try building gcc from source if you haven't till now, refer the docs
  https://gcc.gnu.org/install/ for detailed information and try
  building with bootstrap disabled if you want to save some time. Also
  it is recommended to build a debuggable version ( see next point for
  details ) so that you can efficiently use a debugger to step through
  the source code.

- Once you have a proper version built from source, you can now use a
  debugger ( preferably gdb ) on it to get better understanding of the
  control flow. You can read the official docs (
  https://gcc.gnu.org/wiki/DebuggingGCC#gccbuilddebug ) or the
  gcc-newbies-guide by David Malcolm (
  https://gcc-newbies-guide.readthedocs.io/en/latest/debugging.html )
  for more information and instructions about debugging gcc.

- Speaking of gcc-newbies-guide by David Malcolm, it is actually an
  amazing source to get started for new-comers (
  https://gcc-newbies-guide.readthedocs.io/en/latest/index.html )

Although Google is yet to announce list of selected
organizations. Most of the stuff I mentioned is already present in the
"Before you apply" (
https://gcc.gnu.org/wiki/SummerOfCode#Before_you_apply ) section of
gcc's summer of code page.

- Ankur

> On 13-Feb-2023, at 7:04 PM, Kritika Rag via Gcc  wrote:
> 
> Hello Sir/Mam,
> 
> 
> 
> I’m Kritika Rag, a Computer Science pre-final year undergraduate student
> from India. I’m quite passionate about web development and competitive
> programming and now I’m looking forward to contributing to open-source
> projects. I believe that GSOC 2023 would provide me with the best way to
> start my open-source contribution journey.
> 
> 
> 
> Since I’m a competitive programmer, I have excellent command over Data
> Structures & Algorithms and my primary language is C++, so C++ and GCC are
> something that I use daily, therefore I would love to make my contributions
> to GCC projects. After going through all the projects listed on GCC Wiki
> , these are the
> projects(any one of them) to which I would like to contribute:
> 
>   1. Bug Patrol and primarily Analyze Failing Test Cases – Whether I'm
>   practicing algorithms on Leetcode, GFG, etc., or giving CP contests on
>   CodeChef, Codeforces, etc., Test case failures are something I encounter
>   daily. Working on the project would be an interesting dig for me to learn
>   about the inner workings of something that I see daily and make
>   improvements to it.
>   2.  Library Infrastructure - As quoted *"These tasks are about improving
>   the utility routine library used by GCC. If you like data structures, these
>   may be for you", *and being a data structures enthusiast I do believe
>   that I'll be able to put my best knowledge to use in this project.
> 
> Lastly, thank you so much for providing these opportunities, I would be
> grateful if you would provide me the opportunity to work with your
> organization. Looking forward to hearing from you soon.
> 
> Thanks and Regards,
> Kritika Rag
> 
> 
> 
> Sent from Mail  for Windows

Recommendation of Gmail violates mission to respects users freedom

[David Kleuker]

Hello,
 
since the GCC project seem not to be reachable in the Fediverse (only Twitter 
linked on website), i contact you here about this issue.
 
https://chaos.social/@davidak/109893176873158932
 
The Free Software Foundation and the GNU project promote and create Free 
Software that respects users freedom. The GCC Development Mission Statement is 
"Supporting the goals of the GNU project."
 
So i was surprised to see that you recommend the e-mail providers "Gmail, 
Yahoo, Hotmail, or similar" that are known not to respect the users privacy, on 
https://gcc.gnu.org/bugzilla/createaccount.cgi.
 
I suggest removing the examples since most people coming to the bug tracker 
should know what an e-mail provider is and instead recommend to use an e-mail 
alias to protect from spam on the main address.
 
You should also investigate how this recommendation got there and prevent such 
situations from happening again, as it hurts the reputation of GCC, GNU and the 
FSF! It did it for me.
 
It looks it was added in 2011: 
https://web.archive.org/web/20110611085833/http://gcc.gnu.org/bugzilla/createaccount.cgi
 
Please inform me when you found a solution. (i'm not subscribed to the mailing 
list)
 
kind regards
davidak
 
PS: Thanks for your work on GCC and other Free Software!

Re: Failure During Building

[Iain Sandoe]

> On 19 Feb 2023, at 16:27, -xlan-  wrote:
> 
> Hi, I have the SDK installed but I don't understand how to use the 
> --with-sysroot command. Is the flag supposed to be with my make all-gcc 
> command, please elaborate.

It is a configure argument for GCC’s configure script - there is more 
information here:
https://gcc.gnu.org/install/  (and in the linked pages)

 I guess (in your build script) you have something like 

…/configure —prefix=…. 

the --with-sysroot=…. need to be appended to that.

Iain

Re: Failure During Building

[-xlan- via Gcc]

Hi, I have the SDK installed but I don't understand how to use the
--with-sysroot command. Is the flag supposed to be with my make all-gcc
command, please elaborate.
On Sat, Feb 18, 2023 at 3:49 PM Iain Sandoe  wrote:

> Hi
>
> > On 18 Feb 2023, at 20:28, -xlan-  wrote:
> >
> > I tried compiling version 12.2.0 and it attempts to access system
> headers at /usr/include, but on mac the system headers are stored at
> >
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include.
>
> For supported x86_64 GCC versions (at present 12 and trunk) on macOS12.
>
> It is usually easiest to install the Xcode Command Line Tools - the SDK
> path is then /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
>
> then add the following to your configure line:
>
> —with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk
>
> If you want to use the set in Xcode then add the following to your
> configure line:
>
> —with-sysroot=`xcrun --show-sdk-path`
>
> I prefer/recommend the first option.
> HTH,
> Iain
>
>
>

Re: Recommendation of Gmail violates mission to respects users freedom

[Jonathan Wakely via Gcc]

On Mon, 20 Feb 2023 at 10:39, David Kleuker wrote:
>
> Hello,
>
> since the GCC project seem not to be reachable in the Fediverse (only Twitter 
> linked on website), i contact you here about this issue.
>
> https://chaos.social/@davidak/109893176873158932
>
> The Free Software Foundation and the GNU project promote and create Free 
> Software that respects users freedom. The GCC Development Mission Statement 
> is "Supporting the goals of the GNU project."
>
> So i was surprised to see that you recommend the e-mail providers "Gmail, 
> Yahoo, Hotmail, or similar" that are known not to respect the users privacy, 
> on https://gcc.gnu.org/bugzilla/createaccount.cgi.
>
> I suggest removing the examples since most people coming to the bug tracker 
> should know what an e-mail provider is and instead recommend to use an e-mail 
> alias to protect from spam on the main address.

I think we should just drop the recommendation to use a throwaway
email account. Or water it down to a much weaker suggestion ("The
email address linked to your account might become publicly visible, so
if you are concerned about corporate email addresses or other
non-public email addresses being exposed, you might want to consider
using a different address for your bugzilla account").

Bugzilla doesn't show email addresses to non-logged in users, and
account creation is restricted to stop spammers logging in now. Email
addresses are shown in barely obfuscated form at
https://gcc.gnu.org/pipermail/gcc-bugs/2023-February/812879.html but
nowadays spammers have plenty of ways to obtain email addresses that
don't rely on scraping web pages. I'm not sure the emphasized
recommendation to use web mail accounts really makes sense. What if my
primary email account is a web mail account? Does that make me safer
from spam? Or should I create a second webmail account just for GCC
bugzilla? I think we should just let users decide how to manage their
own email infosec.

Re: Failure During Building

[-xlan- via Gcc]

Thanks, I'll check it out.

On Sun, Feb 19, 2023 at 8:48 AM Iain Sandoe  wrote:

>
>
> > On 19 Feb 2023, at 16:27, -xlan-  wrote:
> >
> > Hi, I have the SDK installed but I don't understand how to use the
> --with-sysroot command. Is the flag supposed to be with my make all-gcc
> command, please elaborate.
>
> It is a configure argument for GCC’s configure script - there is more
> information here:
> https://gcc.gnu.org/install/  (and in the linked pages)
>
>  I guess (in your build script) you have something like
>
> …/configure —prefix=….
>
> the --with-sysroot=…. need to be appended to that.
>
> Iain
>
>

MicroBlaze symver attribute support

[Vincent Fazio via Gcc]

Michael, all,

Regarding:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101766
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102110

If I understand correctly, since the GCC MicroBlaze targets generate ELF
images, it would seem there's no technical reason why `__attribute__
((symver ...))` cannot be supported?

The issue seems to be that the MicroBlaze targets in config.gcc do not
include elfos.h
https://github.com/gcc-mirror/gcc/blob/master/gcc/config.gcc#L2369

Which defines `ASM_OUTPUT_SYMVER_DIRECTIVE`
https://github.com/gcc-mirror/gcc/blob/master/gcc/config/elfos.h#L259

Which is necessary for
https://github.com/gcc-mirror/gcc/blob/master/gcc/varasm.cc#L6260

Changing the targets to include elfos.h leads to a number of conflicts with
the target specific header (config/microblaze/microblaze.h).

Should `ASM_OUTPUT_SYMVER_DIRECTIVE` be copied into
config/microblaze/microblaze.h or should the MicroBlaze targets and header
be reworked to support elfos.h?

I'm asking because I've seen a number of projects run into this issue (xz,
elfutils, libfuse, libkcapi, cryptsetup).

Thanks,
-Vincent

Re: MicroBlaze symver attribute support

[Joel Sherrill]

On Mon, Feb 20, 2023 at 7:56 AM Vincent Fazio via Gcc 
wrote:

> Michael, all,
>
> Regarding:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101766
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102110
>
> If I understand correctly, since the GCC MicroBlaze targets generate ELF
> images, it would seem there's no technical reason why `__attribute__
> ((symver ...))` cannot be supported?
>
> The issue seems to be that the MicroBlaze targets in config.gcc do not
> include elfos.h
> https://github.com/gcc-mirror/gcc/blob/master/gcc/config.gcc#L2369
>
> Which defines `ASM_OUTPUT_SYMVER_DIRECTIVE`
> https://github.com/gcc-mirror/gcc/blob/master/gcc/config/elfos.h#L259
>
> Which is necessary for
> https://github.com/gcc-mirror/gcc/blob/master/gcc/varasm.cc#L6260
>
> Changing the targets to include elfos.h leads to a number of conflicts with
> the target specific header (config/microblaze/microblaze.h).
>
> Should `ASM_OUTPUT_SYMVER_DIRECTIVE` be copied into
> config/microblaze/microblaze.h or should the MicroBlaze targets and header
> be reworked to support elfos.h?
>

IMO reworked to include elfos.h. During the RTEMS port, we noticed that
some quirks on the microblaze gcc because it isn't using elfos.h. This
likely
will mean it will be updated as a side-effect of normal GCC maintenance
instead of being an odd singleton which doesn't share.

>
> I'm asking because I've seen a number of projects run into this issue (xz,
> elfutils, libfuse, libkcapi, cryptsetup).
>

And RTEMS.

--joel

>
> Thanks,
> -Vincent
>

[GSoC] Help needed for building on aarch64-apple-darwin22.1.0

[Shengyu Huang via Gcc]

Dear all,

After following the instructions here (https://gcc.gnu.org/wiki/InstallingGCC) 
and here (https://gcc.gnu.org/install/index.html), the `make` step simply fails 
with “*** Configuration aarch64-apple-darwin22.1.0 not supported”. I found this 
issue on Bugzilla (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168), but the 
status says it’s suspended. Does it mean there is no way I can build from 
source on my new laptop? My old MBP was unfortunately broken two months ago, so 
the new laptop with Apple M2 is the only device I have at the moment.

Best,
Shengyu

Re: [GSoC] Help needed for building on aarch64-apple-darwin22.1.0

[Iain Sandoe]

Hi Shengyu,

> On 20 Feb 2023, at 17:31, Shengyu Huang via Gcc  wrote:
> 

> After following the instructions here 
> (https://gcc.gnu.org/wiki/InstallingGCC) and here 
> (https://gcc.gnu.org/install/index.html), the `make` step simply fails with 
> “*** Configuration aarch64-apple-darwin22.1.0 not supported”. I found this 
> issue on Bugzilla (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168), but 
> the status says it’s suspended. Does it mean there is no way I can build from 
> source on my new laptop? My old MBP was unfortunately broken two months ago, 
> so the new laptop with Apple M2 is the only device I have at the moment.

I have a development branch for trunk here :
  https://github.com/iains/gcc-darwin-arm64
and for GCC-12 here:
 https://github.com/iains/gcc-12-branch

until I have some time to upstream the work (which could not be before GCC-14, 
I think) you can use these.

HTH,
Iain

Re: Problems when building NT kernel drivers with GCC / LD

[Pali Rohár via Gcc]

On Tuesday 03 January 2023 11:06:26 Nick Clifton wrote:
> Hi Pali,
> 
> > Hello! I would like to remind this thread for gcc/binutils developers.
> > Most of these issues are still present and cause problems for compiling
> > native PE binary. If you have questions or you need any other information
> > please let me know.
> 
> Have bug reports been filed for the individual issues ?  If not, please
> could they be created.  The URLs for filing bugs are:
> 
>   https://sourceware.org/bugzilla/enter_bug.cgi?product=binutils
>   https://gcc.gnu.org/bugzilla/enter_bug.cgi
> 
> It would *really* help if the bug reports include a simple test case
> to reproduce the specific problems.
> 
> If it is not clear which tool is the source of the problem, then I would
> suggest choosing the binutils first.  If it turns out that specific issue
> is actually caused by a problem in gcc, the bug report can always be moved
> later on.
> 
> Cheers
>   Nick
> 

Hello! Just for a record, I filled individual issues to bugzilla:
https://sourceware.org/bugzilla/show_bug.cgi?id=30004
https://sourceware.org/bugzilla/show_bug.cgi?id=30139
https://sourceware.org/bugzilla/show_bug.cgi?id=30140
https://sourceware.org/bugzilla/show_bug.cgi?id=30141
https://sourceware.org/bugzilla/show_bug.cgi?id=30142
https://sourceware.org/bugzilla/show_bug.cgi?id=30143
https://sourceware.org/bugzilla/show_bug.cgi?id=30144
https://sourceware.org/bugzilla/show_bug.cgi?id=30145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108851
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108852

Re: MicroBlaze symver attribute support

[Michael Eager]

On 2/20/23 06:54, Joel Sherrill wrote:



On Mon, Feb 20, 2023 at 7:56 AM Vincent Fazio via Gcc > wrote:


Michael, all,

Regarding:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101766

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102110


If I understand correctly, since the GCC MicroBlaze targets generate ELF
images, it would seem there's no technical reason why `__attribute__
((symver ...))` cannot be supported?

The issue seems to be that the MicroBlaze targets in config.gcc do not
include elfos.h
https://github.com/gcc-mirror/gcc/blob/master/gcc/config.gcc#L2369


Which defines `ASM_OUTPUT_SYMVER_DIRECTIVE`
https://github.com/gcc-mirror/gcc/blob/master/gcc/config/elfos.h#L259 


Which is necessary for
https://github.com/gcc-mirror/gcc/blob/master/gcc/varasm.cc#L6260


Changing the targets to include elfos.h leads to a number of
conflicts with
the target specific header (config/microblaze/microblaze.h).

Should `ASM_OUTPUT_SYMVER_DIRECTIVE` be copied into
config/microblaze/microblaze.h or should the MicroBlaze targets and
header
be reworked to support elfos.h?


IMO reworked to include elfos.h. During the RTEMS port, we noticed that
some quirks on the microblaze gcc because it isn't using elfos.h. This 
likely

will mean it will be updated as a side-effect of normal GCC maintenance
instead of being an odd singleton which doesn't share.


I'm asking because I've seen a number of projects run into this
issue (xz,
elfutils, libfuse, libkcapi, cryptsetup).


And RTEMS.

--joel



Joel -- do you have a patch to add elfos.h to MicroBlaze?

--
Michael Eager