Re: [RFC] Closing of all remaining Bugzilla PRs against powerpcspe

2020-05-25 Thread Eric Gallager via Gcc
On 5/25/20, Arseny Solokha wrote: > Hi, > > >>> >> PRs from the second group were filed by me, so if there's consensus to >>> >> close all >>> >> of them, the ones from this second group I can close myself. I don't >>> >> have the >>> >> right permissions to modify PRs reported by someone else, so

WWDC thread: support for darwin/macOS going forward

2020-06-22 Thread Eric Gallager via Gcc
Hi, at Apple's WWDC this year they have announced that they are doing yet another architecture transition, so I was wondering what exactly would be the best way to go about adding support for it? The first issue would be just what to call the new architecture; it seems to be ARM-based, but there mi

Re: Copyright assignment for Rust-GCC

2021-01-04 Thread Eric Gallager via Gcc
On Mon, Jan 4, 2021 at 11:13 AM David Edelsohn via Gcc wrote: > On Mon, Jan 4, 2021 at 5:29 AM Nala Ginrut via Gcc > wrote: > > > > Hi Folks! > > This mail is about the development of Rust frontend of GCC. > > > > To avoid misunderstanding, please let me introduce Rust-GCC briefly. > > In 2013,

Re: Static analysis updates in GCC 11

2021-01-29 Thread Eric Gallager via Gcc
On Sat, Jan 30, 2021 at 2:29 AM Eric Gallager wrote: > > On Thu, Jan 28, 2021 at 3:24 PM David Malcolm via Gcc wrote: > > > > I wrote a blog post covering what I've been working on in the analyzer > > in this release: > > > > https://developers.redhat.com/blog/2021/01/28/static-analysis-updates

Freenode changing ownership

2021-05-19 Thread Eric Gallager via Gcc
Recently I have noticed a post going around various FOSS circles about Freenode changing hands: https://gist.github.com/joepie91/df80d8d36cd9d1bde46ba018af497409 I also checked the GCC wiki, and on both its main page and its GCConIRC page it advertises an IRC channel on Freenode for GCC: https://gc

Re: Update to GCC copyright assignment policy

2021-06-01 Thread Eric Gallager via Gcc
On Tue, Jun 1, 2021 at 10:02 AM David Edelsohn via Gcc wrote: > > GCC was created as part of the GNU Project but has grown to operate as > an autonomous project. > > The GCC Steering Committee has decided to relax the requirement to > assign copyright for all changes to the Free Software Foundatio

Re: gcc plugin on MacOS failure

2021-07-23 Thread Eric Gallager via Gcc
On Thu, Jul 22, 2021 at 4:18 PM Iain Sandoe via Gcc wrote: > > > > > On 22 Jul 2021, at 20:41, Andrew Pinski via Gcc wrote: > > > > On Thu, Jul 22, 2021 at 7:37 AM Marc wrote: > >> > > >> I have a gcc plugin (for afl++, > >> https://github.com/AFLplusplus/AFLplusplus) that works fine when > >> c

Listing deprecated targets in changes.html

2021-09-13 Thread Eric Gallager via Gcc
Hi, I see that a number of targets are going to be deprecated for GCC 12: - m32r{,le}-linux: https://gcc.gnu.org/pipermail/gcc-patches/2021-September/579265.html - cr16: https://gcc.gnu.org/pipermail/gcc-patches/2021-September/579280.html - m68k-openbsd: https://gcc.gnu.org/pipermail/gcc-patches/20

Re: [FYI] bugzilla cleanup

2021-09-18 Thread Eric Gallager via Gcc
On Thu, Sep 16, 2021 at 11:45 AM Martin Sebor via Gcc wrote: > > On 9/14/21 2:10 AM, Andrew Pinski via Gcc wrote: > > Hi all, > >I am doing some bugzilla cleanup. This includes disabling some > > components and some versions for new bugs. > > So far I have disabled versions before GCC 4 becau

Re: Can gcc itself be tested with ubsan? If so, how?

2021-09-28 Thread Eric Gallager via Gcc
On Tue, Sep 28, 2021 at 2:48 AM Toon Moene wrote: > > On 9/28/21 8:35 AM, Erick Ochoa via Gcc wrote: > > >> Can ubsan be used on the compiler itself? > > I regularly build the compiler(s) natively with ubsan enabled, see for > instance: > > https://gcc.gnu.org/pipermail/gcc-testresults/2021-Septem

Re: Generating GCC Documentation

2021-11-11 Thread Eric Gallager via Gcc
On Wed, Nov 10, 2021 at 9:26 AM Joel Sherrill wrote: > > Thanks for the quick reply. > > On Wed, Nov 10, 2021 at 8:20 AM Jonathan Wakely wrote: > > > > On Wed, 10 Nov 2021 at 14:08, Joel Sherrill wrote: > > > > > > Hi > > > > > > It's been a while since I tried this and it appears things have > >

Re: Help with an ABI peculiarity

2022-01-11 Thread Eric Gallager via Gcc
On Mon, Jan 10, 2022 at 8:28 AM Iain Sandoe wrote: > > Hi Florian, > > > On 10 Jan 2022, at 08:38, Florian Weimer wrote: > > > > * Jeff Law via Gcc: > > > >> Most targets these days use registers for parameter passing and > >> obviously we can run out of registers on all of them. The key > >> pr

Re: git hooks: too strict check

2022-01-14 Thread Eric Gallager via Gcc
On Fri, Jan 14, 2022 at 11:14 AM Michael Matz via Gcc wrote: > > Hello, > > On Fri, 14 Jan 2022, Martin Liška wrote: > > > Hello. > > > > I'm working on a testsuite clean-up where some of the files are wrongly > > named. > > More precisely, so files have .cc extension and should use .C. However

Re: No type checking in ctype builtins

2022-04-28 Thread Eric Gallager via Gcc
On Wed, Apr 27, 2022 at 12:20 PM Jonathan Wakely via Gcc wrote: > > On Wed, 27 Apr 2022 at 16:29, Andrea Monaco via Gcc wrote: > > > > > > This program > > > > #include > > > > int main () > > { > > char *s; > > isspace (s); > > } > > > > compiles with no warning in gcc 8.3.0, ev

Re: How to regenerate aclocal.m4?

2022-05-02 Thread Eric Gallager via Gcc
On Sun, May 1, 2022 at 7:09 PM Maciej W. Rozycki wrote: > > On Sat, 30 Apr 2022, Zopolis0 via Gcc wrote: > > > 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 f

Re: [RFC] Support for nonzero attribute

2022-06-08 Thread Eric Gallager via Gcc
On Sun, Jun 5, 2022 at 4:10 PM Miika via Gcc wrote: > > Based on Jakub's and Yair's comments I created a new attribute "inrange". > Inrage takes three arguments, pos min and max. > Pos being the argument position in the function, and min and max defines the > range of valid integer. Both min and m

Re: [RFC] Support for nonzero attribute

2022-06-08 Thread Eric Gallager via Gcc
On Wed, Jun 8, 2022 at 5:00 PM Miika wrote: > > On Wednesday, June 8th, 2022 at 8:42 PM, Eric Gallager > wrote: > > Could you take a look at bug 78155 too? There was a request to add > > something like this in that bug: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78155 > > (and I think I've

Re: New "Diving into GCC internals" section in newbies guide

2022-06-12 Thread Eric Gallager via Gcc
On Sun, Jun 12, 2022 at 12:38 PM David Malcolm via Gcc wrote: > > On Sat, 2022-06-11 at 02:35 +0200, Eric Botcazou wrote: > > > Hope this is helpful; please let me know if you see any mistakes, > > > or if > > > there's room for improvement > > > > Nice work! In the "inside cc1" chapter, I think

Re: remove intl/ directory?

2022-06-20 Thread Eric Gallager via Gcc
On Sat, Jun 18, 2022 at 1:01 PM Bruno Haible wrote: > > Hi, > > As the long-term GNU gettext maintainer, I would suggest to remove the intl/ > directory from the GCC distribution. > > The effect for the users would be: > * On systems without glibc, users who want an internationalized GCC > i

Re: remove intl/ directory?

2022-06-23 Thread Eric Gallager via Gcc
On Thu, Jun 23, 2022 at 12:25 AM Bruno Haible wrote: > > Iain Sandoe wrote: > > Yes ( > > # We can use an in-tree build of libintl. > > if test -f ifelse([$1],,[../gettext-runtime],[$1])/uninstalled-config.sh; > > then > > > > relative_builddir='ifelse([$1],,[${top_builddir}/..],[$1]/..)/gett

Re: New/improved warning option for padding bytes

2022-08-21 Thread Eric Gallager via Gcc
On Fri, Aug 19, 2022 at 6:13 AM Jonas Rahlf via Gcc wrote: > > As a firmware developer I would appreciate a warning option about padding > bytes, but only for such cases where you can reduce the number of padding > bytes by rearranging the fields. > > The current -Wpadded warns about all padding b

Humor in GCC

2023-04-01 Thread Eric Gallager via Gcc
Happy April Fools' Day! In the spirit of the day, I've done a brief survey of humor in other FOSS projects, and how they could be used as inspiration for fun features in GCC. * Emacs: The etc/ folder in the emacs sources has plenty of humorous material in it, most obviously, etc/JOKES (although, s

Re: More C type errors by default for GCC 14

2023-05-10 Thread Eric Gallager via Gcc
On 5/9/23, Jonathan Wakely via Gcc wrote: > On Tue, 9 May 2023 at 23:38, Joel Sherrill wrote: >> We are currently using gcc 12 and specifying C11. To experiment with >> these stricter warnings and slowly address them, would we need to build >> with a newer C version? > > No, the proposed changes

Re: More C type errors by default for GCC 14

2023-05-15 Thread Eric Gallager via Gcc
On 5/15/23, Richard Earnshaw (lists) via Gcc wrote: > On 10/05/2023 03:38, Eli Zaretskii via Gcc wrote: >>> From: Arsen Arsenović >>> Cc: Eli Zaretskii , Jakub Jelinek , >>> jwakely@gmail.com, gcc@gcc.gnu.org >>> Date: Tue, 09 May 2023 22:21:03 +0200 >>> The concern is using the good w

Re: Warning specifically for a returning noreturn

2023-07-05 Thread Eric Gallager via Gcc
On Wed, Jul 5, 2023 at 7:28 AM Jonathan Wakely via Gcc wrote: > > On Wed, 5 Jul 2023 at 12:01, Julian Waters via Gcc wrote: > > > > I see, thanks Andrew. > > > > Anyone else have opinions on this besides Liu or Andrew? The responses have > > been surprisingly quiet thus far > > IMHO all warnings

Re: GNU Tools Cauldron 2024

2024-03-06 Thread Eric Gallager via Gcc
On Tue, Mar 5, 2024 at 11:01 PM Bradley M. Kuhn via Gcc wrote: > > Jeremy, David, Carlos, and the GCC Community, > > Jeremy Bennett wrote yesterday: > > We are starting to put together the plans for this year's Cauldron. We > > have a suggested date of 13-15 September, the weekend before LPC. > >

Re: [RFC] add regenerate Makefile target

2024-03-15 Thread Eric Gallager via Gcc
On Fri, Mar 15, 2024 at 4:53 AM Christophe Lyon via Gcc wrote: > > On Thu, 14 Mar 2024 at 19:10, Simon Marchi wrote: > > > > > > > > On 2024-03-13 04:02, Christophe Lyon via Gdb wrote: > > > Hi! > > > > > > After recent discussions on IRC and on the lists about maintainer-mode > > > and various p

Re: [RFC] add regenerate Makefile target

2024-03-20 Thread Eric Gallager via Gcc
On Tue, Mar 19, 2024 at 2:10 PM Tom Tromey wrote: > > > not sure if the current autoregen.py is in sync with that? > > I'm curious why "autoreconf -f" is insufficient. > It seems to me that this should work. `autoreconf -f` works fine in individual subdirectories, the problem is that the top-leve

Re: SARIF support in GCC: wiki page and BZ keyword

2024-06-21 Thread Eric Gallager via Gcc
On Fri, Jun 21, 2024 at 12:12 PM David Malcolm via Gcc wrote: > > I've create a wiki page to track our support for GCC: > https://gcc.gnu.org/wiki/SARIF > > and a keyword "SARIF" in our bugzilla instance for bugs relating to it > (see links on the above page). > Hi, thanks for creating these. S

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.

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

2024-08-23 Thread Eric Gallager via Gcc
On Thu, Aug 22, 2024 at 1:27 PM Gerald Pfeifer wrote: > > On Mon, 19 Aug 2024, Eric Gallager via Gcc-cvs-wwwdocs wrote: > > This is an automated email from the git hooks/post-receive script. It was > > generated because a ref change was pushed to the repository containing &g

Re: #pragma once behavior

2024-09-07 Thread Eric Gallager via Gcc
On Sat, Sep 7, 2024 at 5:34 AM Richard Biener via Gcc wrote: > > > > > Am 07.09.2024 um 07:27 schrieb Jeremy Rifkin : > > > >  > >> > >> This is why I said what is the a same file if you can't rely on inodes > >> working? > > > > I don't have a good answer for such a case. Of course, no matter h

Re: Update bootstrap requirement to C++14?

2024-09-14 Thread Eric Gallager via Gcc
On Sat, Sep 14, 2024 at 11:53 AM Jason Merrill via Gcc wrote: > > We moved to a bootstrap requirement of C++11 in GCC 11, 8 years after > support was stable in GCC 4.8. > > It is now 8 years since C++14 was the default mode in GCC 6 (and 9 years > since support was complete in GCC 5); perhaps it's

Re: Is -Wtraditional obsolete?

2024-10-16 Thread Eric Gallager via Gcc
On Wed, Oct 16, 2024 at 2:52 PM Arsen Arsenović via Gcc wrote: > > Eli Zaretskii via Gcc writes: > > > Please don't remove the support for -Wtraditional if it's easy to fix. > > Removing it runs risk of breaking someone's program, so unless keeping > > it is a real dumper on GCC development, I ho

Re: Is -Wtraditional obsolete?

2024-10-16 Thread Eric Gallager via Gcc
On Wed, Oct 16, 2024 at 4:29 PM Joseph Myers wrote: > > On Wed, 16 Oct 2024, Eric Gallager via Gcc wrote: > > > One thing about -Wtraditional is that it enables a lot of different > > messages, so I always thought it would make more sense as an umbrella > > warning t

Re: Sourceware forge experiment

2024-10-24 Thread Eric Gallager via Gcc
On Sun, Oct 20, 2024 at 9:27 PM Mark Wielaard wrote: > > As an experiment Sourceware is now running an forgejo v9 instance at > https://forge.sourceware.org > > Everybody with an @sourceware.org, @cygwin.com or @gcc.gnu.org address > can register an account (please use the same user name as your a

Re: On pull request workflows for the GNU toolchain

2024-09-23 Thread Eric Gallager via Gcc
On Mon, Sep 23, 2024 at 8:09 AM Thomas Koenig via Gcc wrote: > > [For the fortran people: Discussion on gcc@] > > Just a general remark. > > There are people, such as myself, who regularly mess up > their git repositories because they have no mental model > of what git is doing (case in point: The

Re: Passing a hidden argument in a dedicated register

2024-12-27 Thread Eric Gallager via Gcc
On Mon, Dec 16, 2024 at 11:43 AM Alexander Monakov wrote: > > > On Mon, 16 Dec 2024, Florian Weimer via Gcc wrote: > > > I would like to provide a facility to create wrapper functions without > > lots of argument shuffling. To achieve that, the wrapping function and > > the wrapped function shoul