Re: GCC Multi-Threading Ideas

On 1/24/20, Richard Earnshaw (lists) wrote: > On 24/01/2020 10:27, Jonathan Wakely wrote: >> On Fri, 24 Jan 2020 at 03:39, Nicholas Krause >> wrote: >>> Sorry for the second message Allan but make -j does not scale well >>> beyond 4 or >>> 8 threads and that's considering a 4 core or 8 machine. T

Re: sprintf warning on overlapping output

On 9/25/16, Bernd Edlinger wrote: > Hi Martin, > > in the past I have seen (and fixed) code like > > sprintf(buf, "%s %d", buf, x); > > that may possibly work by chance, but usually > produces undefined results. > > Do you see a way to enhance the warning for cases > where the output buffer overla

Lint-style comments, more generally

Seeing how long the thread on gcc-patches on what comments -Wimplicit-fallthrough should recognize has gotten, I thought it might be a good idea to start a discussion on lint-style comments more generally. Instead of just limiting the use of lint-style comments to -Wimplicit-fallthrough, why not sp

Re: GCC 7.0.0 Status Report (2016-10-21)

On Fri, Oct 21, 2016 at 9:46 AM, Jakub Jelinek wrote: > Status > == > > Trunk which will eventually become GCC 7 is still in Stage 1 but its > end is near and we are planning to transition into Stage 3 starting > Nov 13th end of day time zone of your choice. > > This means it is time to get th

Re: History of GCC

On 10/26/16, Ian Lance Taylor wrote: > On Wed, Oct 26, 2016 at 9:31 AM, Will Hawkins wrote: >> >> Thank you for your response! I don't think that there has to be >> controversy to be interesting. Obviously that split/reunification was >> important, but I think that there might even be some value

Re: warning: conversion from ‘int’ to ‘char’ may change value

On 9/20/18, Martin Sebor wrote: > On 09/20/2018 08:08 AM, Vincent Lefevre wrote: >> On 2018-09-17 10:03:48 -0600, Martin Sebor wrote: >>> On 09/17/2018 06:00 AM, Umesh Kalappa wrote: Hi All, When we try to compile the below case from trunk gcc we get the below warning (-Wconver

Re: GCC 6 branch is now closed

On 10/26/18, Jakub Jelinek wrote: > After the GCC 6.5 release the GCC 6 branch is now closed. Please > refrain from committing to it from now on. > > Thanks > Jakub > So, since it's the last branch with java in it, can we go and finally remove the last vestiges of java from the gcc website

Re: Regarding projects and begineer guide.

On 12/5/18, David Malcolm wrote: > On Wed, 2018-12-05 at 22:48 +0530, Durgesh Kumar wrote: >> Dear sir/mam >> I am durgesh kumar from ABES engineering collenge,ghaziabad,uttar >> pradesh,india. >> >> I am currently in 2nd year of my graduation(Btech CSE ) >> >> I want to contribute in some of your

Re: GSoC Project Ideas

On 3/3/19, Patrick Palka wrote: > Hi everyone, > > I am very interested in working on GCC as part of GSoC this year. A few > years > ago I was a somewhat active code contributor[1] and unfortunately my > contributing waned once I went back to school, but I'm excited to > potentially > have the op

Re: Warning for C Parameter Name Mismatch

On 3/8/19, David Brown wrote: > On 09/03/2019 00:06, Joseph Myers wrote: >> On Fri, 8 Mar 2019, Joel Sherrill wrote: >> >>> Can gcc report when the parameter name in a C prototype >>> does not match that used in the implementation? >>> >>> int f(int x); >>> >>> int f(int y) {...} >> >> I think thi

Re: [RFC] split of i386.c

On 3/12/19, Martin Liška wrote: > Hi. > > I've thinking about the file split about quite some time, mainly > in context of PR84402. I would like to discuss if it's fine for > maintainers of the target to make such split and into which logical > components can the file be split? > > I'm suggesting

Re: How to add %' into gfc_fatal_error

On 3/11/19, Martin Sebor wrote: > On 3/11/19 8:18 AM, Martin Liška wrote: >> Hi. >> >> I would like to add %' into __gcc_gfc__ in order to handle: >> >> ./xgcc -B. /tmp/module.ii -Wformat -c >> /home/marxin/Programming/gcc/gcc/fortran/module.c: In function ‘void >> dump_module(const char*, int)’:

Re: Warning for C Parameter Name Mismatch

On 3/8/19, Joel Sherrill wrote: > Hi > > This may be just an ignorant user question on my part. > > Can gcc report when the parameter name in a C prototype > does not match that used in the implementation? > > int f(int x); > > int f(int y) {...} > > We try to fix every warning gcc reports but thi

Re: GSOC Proposal

On 3/29/19, nick wrote: > > > On 2019-03-29 10:28 a.m., nick wrote: >> >> >> On 2019-03-29 5:08 a.m., Richard Biener wrote: >>> On Thu, 28 Mar 2019, nick wrote: >>> On 2019-03-28 4:59 a.m., Richard Biener wrote: > On Wed, Mar 27, 2019 at 6:31 PM nick wrote: >> >> Greeti

Re: [RFC/RFA] Obsolete Cell Broadband Engine SPU targets

On 4/2/19, Ulrich Weigand wrote: > Hello, > > the spu-elf target in GCC supports generating code for the SPU processors > of the Cell Broadband Engine; it has been part of upstream GCC since 2008. > > However, at this point I believe this target is no longer in use: > - There is no supported Cell/

Re: Iain Sandoe appointed Darwin co-maintainer

Congrats Iain on having your "de facto" maintainer status upgraded to being official! On 4/19/19, David Edelsohn wrote: > I am pleased to announce that the GCC Steering Committee has > appointed Iain Sandoe as Darwin co-maintainer. > > Please join me in congratulating Iain on his new

Re: About GSOC.

On 5/31/19, Nathan Sidwell wrote: > On 5/30/19 5:38 PM, Segher Boessenkool wrote: >> On Thu, May 30, 2019 at 07:08:45PM +0200, Martin Jambor wrote: >>> Interesting, I was also puzzled for a moment. But notice that: >>> >>> int main () >>> { >>> _Float128 x = 18446744073709551617.5f128; >>>

Re: Enabling Ctags Tree Wide for GCC

On 9/11/19, Nicholas Krause wrote: > Greetings, > > I was wondering what is the easiest way to allow source tree wide ctags. > There doesn't > > seem to be a make x command for it nor any real documentation online and > it would > > be nice to have. > ISTR this topic coming up 2 years ago: https:

Re: Moving to C++11

On 9/26/19, Nicholas Krause wrote: > Greetings, > > I asked about moving to C/C++ 11 as it would make it easier to > > allow multithreading support due to having a memory model > > alongside other features. Jason Merill mentioned due to it > > being so common it may be a good time to. > > Moving

Re: GCC selftest improvements

On 10/25/19, Gabriel Dos Reis via gcc wrote: > [Andrew] > > | > GCC has some rather unique requirements, in that we support a great > many > | > build configurations, some of which are rather primitive - for example, > | > requiring just C++98 with exceptions disabled, in that we want to be > able

Re: GCC selftest improvements

On 10/31/19, Pedro Alves wrote: > On 10/26/19 11:46 PM, Eric Gallager wrote: > >> Nicholas Krause was also wanting to move to C++11 recently: >> https://gcc.gnu.org/ml/gcc/2019-10/msg00110.html (this month) >> https://gcc.gnu.org/ml/gcc/2019-09/msg00228.html (last mon

Re: [RFC] Characters per line: from punch card (80) to line printer (132)

On 12/5/19, Andrew Stubbs wrote: > On 05/12/2019 16:17, Joseph Myers wrote: >> Longer lines mean less space for multiple terminal / editor windows >> side-by-side to look at different pieces of code. I don't think that's >> an >> improvement. > > Here's a data-point > > My 1920 pixel-wide sc

Re: C2X Proposal, merge '.' and '->' C operators

On 12/16/19, J Decker wrote: > Here's the gist of what I would propose... > https://gist.github.com/d3x0r/f496d0032476ed8b6f980f7ed31280da > > In C, there are two operators . and -> used to access members of struct and > union types. These operators are specified such that they are always paired >

Re: Doxygen for GCC

On 6/8/17, Martin Liška wrote: > On 04/28/2017 02:32 PM, Martin Liška wrote: >> I'm planning to periodically build it and rsync to a public website. >> I guess, sometimes it can be handy. > > Done that (it's weekly updated): > > http://gcc.opensuse.org/gcc-doxygen/ > > Martin > Clicking on the fi

Re: Missing warning opportunity - code after break;

On 6/19/17, Soul Studios wrote: > Just noticed this: > while(something) > { > // stuff > > if (num_elements == 0) > { > break; > --current_group; > } > } > > doesn't trigger a warning in GCC 5.1, 6.3 and 7.1. The line after > "break;" is unused,

Re: Could preprocessor warn for unsafe macros and side-effects?

On 7/12/17, Martin Sebor wrote: > On 07/11/2017 11:50 PM, sa...@hederstierna.com wrote: >> Hi >> >> Reading about macro pitfalls and eg duplication side-effects >> https://gcc.gnu.org/onlinedocs/cpp/Macro-Pitfalls.html#Macro-Pitfalls >> >> would it be possible to let the preprocessor generate warn

Re: Killing old dead bugs

On 7/18/17, Yuri Gribov wrote: > On Tue, Jul 18, 2017 at 3:54 PM, Martin Sebor wrote: >> On 07/17/2017 02:25 PM, Yuri Gribov wrote: >>> >>> On Mon, Jul 17, 2017 at 4:23 PM, Martin Sebor wrote: On 07/17/2017 02:14 AM, Yuri Gribov wrote: > > > Hi Mikhail, > > On Sun,

Re: Killing old dead bugs

On 7/19/17, Yuri Gribov wrote: > On Wed, Jul 19, 2017 at 7:15 PM, Eric Gallager > wrote: >> On 7/18/17, Yuri Gribov wrote: >>> On Tue, Jul 18, 2017 at 3:54 PM, Martin Sebor wrote: >>>> On 07/17/2017 02:25 PM, Yuri Gribov wrote: >>>>> >

Re: Overwhelmed by GCC frustration

On 8/1/17, Richard Biener wrote: > On Mon, Jul 31, 2017 at 7:08 PM, Andrew Haley wrote: >> On 31/07/17 17:12, Oleg Endo wrote: >>> On Mon, 2017-07-31 at 15:25 +0200, Georg-Johann Lay wrote: Around 2010, someone who used a code snipped that I published in a wiki, reported that the code d

Re: Overwhelmed by GCC frustration

On 8/1/17, Jakub Jelinek wrote: > On Tue, Aug 01, 2017 at 07:08:41AM -0400, Eric Gallager wrote: >> > Heh. I suspect -Os would benefit from a separate compilation pipeline >> > such as -Og. Nowadays the early optimization pipeline is what you >> > want (mostly s

Re: [Bug web/?????] New: Fwd: failure notice: Bugzilla down.

On 8/15/17, Jonathan Wakely wrote: > On 15 August 2017 at 04:10, Martin Sebor wrote: >> On 08/14/2017 04:22 PM, Eric Gallager wrote: >>> >>> I'm emailing this manually to the list because Bugzilla is down and I >>> can't file a bug on Bugzilla ab

Re: Optimization breaks inline asm code w/ptrs

On 8/14/17, Alan Modra wrote: > On Sun, Aug 13, 2017 at 10:25:14PM +0930, Alan Modra wrote: >> On Sun, Aug 13, 2017 at 03:35:15AM -0700, David Wohlferd wrote: >> > Using "m"(*pStr) as an (unused) input parameter has no effect. >> >> Use "m" (*(const void *)pStr) and ignore the warning, or use >> "

Re: [Bug web/?????] New: Fwd: failure notice: Bugzilla down.

On 8/25/17, Szabolcs Nagy wrote: > On 16/08/17 18:38, Joseph Myers wrote: >> On Wed, 16 Aug 2017, Eric Gallager wrote: >>> I see Richi redid all his 7.2 release changes; does that imply that >>> the server restore is now complete? >> >> No, there'

Re: Weird warning when building gcc

On Sat, Sep 23, 2017 at 12:34 PM, nick wrote: > > > On 2017-09-23 12:05 PM, Jeff Law wrote: >> On 09/22/2017 08:25 PM, nick wrote: >>> Greetings All, >>> >>> I am wondering if this is a warning worth looking into or is it just >>> another false postive: >>> >>> /home/nick/gcc/gcc/combine.c:1316:8

Re: Weird warning when building gcc

On Sat, Sep 23, 2017 at 12:34 PM, nick wrote: > If your able to just tell me where the functions are located or how do you > enable ctags for all of > gcc? That would just save me asking stupid questions. Is there a global > setting like make ctags for > doing this or you I have to do it manuall

Re: Weird warning when building gcc

On Mon, Sep 25, 2017 at 11:17 AM, nick wrote: > > > On 2017-09-24 10:10 AM, Eric Gallager wrote: >> On Sat, Sep 23, 2017 at 12:34 PM, nick wrote: >>> If your able to just tell me where the functions are located or how do you >>> enable ctags for all of >&g

Re: RFC: Update top level libtool files

On Tue, Oct 10, 2017 at 11:20 AM, Nick Clifton wrote: > Hi Joseph, > >> As per previous discussions on the issue: it's necessary to revert libtool >> commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c, see >> . > > OK - thanks for that pointer

Re: Feature request: -Wno-unknown-warnings to silently ignore unknown warning control flags.

On Thu, Oct 12, 2017 at 4:46 AM, Oren Ben-Kiki wrote: > Motivation/Use case: > > * Since gcc/g++ intentionally does not have `-Weverything`, there is a > number of explicit `-W...` flags one might wish to specify explicitly. Fair > enough. > > * Additional `-W...` flags are introduced in new gcc/g

Re: Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

On 11/20/17, Yao Qi wrote: > > Hi, > I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some > -Werror=stringop-overflow= and -Werror=stringop-truncation warnings. > Some of them are not necessary to me, > > 1. ../../binutils-gdb/gdb/python/py-gdb-readline.c:79:15: error: ‘char* >

Re: Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

On 11/20/17, Eric Gallager wrote: > On 11/20/17, Yao Qi wrote: >> >> Hi, >> I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some >> -Werror=stringop-overflow= and -Werror=stringop-truncation warnings. >> Some of them are not necessary to me

Re: Possbile patch for compilation errors re possibly uninitialized variables at -Og

On 12/29/17, Louis Krupp wrote: > I tried to build the trunk using: > > BOOT_CFLAGS='-g -Og' CFLAGS_FOR_TARGET='-g -Og' CFLAGS_FOR_BUILD='-g -Og' > > I got a number of compilation warnings -- promoted to errors -- about > possibly uninitialized variables. > > I have what I believe is a decent patc

Re: Possbile patch for compilation errors re possibly uninitialized variables at -Og

iously... > > On Fri, 29 Dec 2017 19:40:38 -0800 Eric Gallager > wrote > > On 12/29/17, Louis Krupp wrote: > > > I tried to build the trunk using: > > > > > > BOOT_CFLAGS='-g -Og' CFLAGS_FOR_TARGET='-g -Og' CFLAGS_FOR

GCC and Meltdown and Spectre vulnerabilities

Is there anything GCC could be doing at the compiler level to mitigate the recently-announced Meltdown and Spectre vulnerabilities? From reading about them, it seems like they involve speculative execution and indirect branch prediction, and those are the domain of things the compiler deals with, r

Re: GCC and Meltdown and Spectre vulnerabilities

On 1/4/18, Will Hawkins wrote: > On Thu, Jan 4, 2018 at 10:10 PM, Eric Gallager > wrote: >> Is there anything GCC could be doing at the compiler level to mitigate >> the recently-announced Meltdown and Spectre vulnerabilities? From >> reading about them, it seems like

Re: GCC and Meltdown and Spectre vulnerabilities

On 1/5/18, Eric Gallager wrote: > On 1/4/18, Will Hawkins wrote: >> On Thu, Jan 4, 2018 at 10:10 PM, Eric Gallager >> wrote: >>> Is there anything GCC could be doing at the compiler level to mitigate >>> the recently-announced Meltdown and Spectre vulnerabili

Re: Google Summer of Code 2018: Call for mentors and ideas

On 1/17/18, Martin Jambor wrote: > Hi, > > following a discussion at IRC about an upcoming deadline to register GCC > as an independent organization for Google Summer of Code 2018 (GSoC), I > have volunteered to serve as the org-admin for GCC if: > > - there is not another volunteer (so step up

Re: Bugzilla timing out

On 1/18/18, Frank Ch. Eigler wrote: > > msebor wrote: > >> I'm having trouble bringing up bugs or updating them. Has anyone else >> noticed Bugzilla (and/or other services running on gcc.gnu.org) being >> very slow or timing out? > > One failed disk in the server has been replaced yesterday. Ple

Re: Blog post about gcc 8 usability improvements

On 3/15/18, David Malcolm wrote: > Sorry for the shameless self-promotion, but I've written up the work > I've done on gcc 8 usability, in blog form, here: > > https://developers.redhat.com/blog/2018/03/15/gcc-8-usability-improvements/ > > I'm working on a patch for the website's changes.html, cov

Re: Gcc bugzilla is down

Confirming, I got the same error message at around 7:29 AM Eastern Daylight Time. Please fix! Eric On 4/1/18, Thomas König wrote: > Hi, > > it seems that gcc bugzilla is currently down, error message is: > > Software error: > > Can't connect to the database. > Error: Can't connect to local MySQL

Re: where should C++ options be documented?

On 4/2/18, Martin Sebor wrote: > Jason, > > The manual mentions some C++-only options in the language > independent section 3.8 Options to Request or Suppress > Warnings and others in 3.5 Options Controlling C++ Dialect. > > For example, -Wcatch-value, -Wconditionally-supported, > and -Wzero-as-nu

Re: Request for compiler option to disable multiple declarations in a single statement

On 4/19/18, Manish Jain wrote: > Hi all, > > One of the historical artefacts of the C language has been the burden of > lugging around multiple declarations in a single statement, with some > well-known pitfalls: > > int* ptr1, ptr2; > > Since ptr2 looks like a pointer but actually is not, standar

Re: Wabi warnings during GCC build

On 6/27/18, Marek Polacek wrote: > On Wed, Jun 27, 2018 at 08:53:48AM -0700, Steve Ellcey wrote: >> Are other people building GCC seeing these messages during the build: >> >> cc1plus: warning: -Wabi won't warn about anything [-Wabi] >> cc1plus: note: -Wabi warns about differences from the most up

Re: [PATCH] Add new tests for --completion option.

On 6/29/18, Martin Liška wrote: > Hi. > > I would like to add some DejaGNU tests for completion option. > > Ready for trunk? > Martin > So, correct me if I'm wrong, but these tests would need to be updated every time a new option starting like one of those is added, right? If so, can you think of

Re: GCC bugzilla is down

On 7/1/18, Jeffrey Walton wrote: > On Sun, Jul 1, 2018 at 4:31 AM, Martin Liška wrote: >> >> Please fix bugzilla: >> https://gcc.gnu.org/bugzilla/ >> >> Can't connect to the database. >> Error: Can't connect to local MySQL server through socket >> '/var/lib/mysql/mysql.sock' (2) >> Is your data

Re: ChangeLog's: do we have to?

On 7/5/18, Aldy Hernandez wrote: > After 20 years of hacking on GCC I feel like I have literally wasted > days of my life typing out ChangeLog entries that could have easily been > generated programmatically. > > Can someone refresh my memory here, what are the remaining arguments for > requiring

Re: Detecting superfluous "else"

On 7/19/18, U.Mutlu wrote: > Hi, > it makes me 'crazy' when I see such if-else constructs: >if (x) > return 7; >else > return 4; > > (Of course in this case one better would use the shorthand "return x ? 7 : > 4;", but that's not the issue here) > > The 'else' is obviously superf

Re: [RFC] Adding Python as a possible language and it's usage

On 7/19/18, Jeff Law wrote: > On 07/18/2018 03:28 PM, Segher Boessenkool wrote: >> On Wed, Jul 18, 2018 at 11:51:36AM +0200, Richard Biener wrote: >>> We already conditionally require Perl for building for some targets so I >>> wonder >>> if using perl would be better ... >> >> At least perl is GP

Re: ChangeLog's: do we have to?

On 7/23/18, Segher Boessenkool wrote: > On Mon, Jul 23, 2018 at 04:03:31PM +0300, Alexander Monakov wrote: >> Not necessarily in the source tree: individual users can put that into >> their >> $XDG_CONFIG_HOME/git/attributes or $HOME/.config/git/attributes. > > And then that user has *all* .md fil

Re: "fall-through" errors

On 7/28/18, Bruce Korb wrote: > ../../autoopts/makeshell.c: In function ‘text_to_var’: > ../../autoopts/makeshell.c:324:14: error: this statement may fall > through [-Werror=implicit-fallthrough=] > (*(opts->pUsageProc))(opts, EXIT_SUCCESS); > ~^~~

Re: gcc 13.2 is missing warnings?

On Thu, Oct 19, 2023 at 7:52 AM Martin Uecker wrote: > > > > Note that the C++ warning is for jumping over a declaration, > which is generally allowed in C but not in C++. > > Martin (Also note that in C, there's -Wjump-misses-init for this, which is enabled by -Wc++-compat, which isn't enabled b

Re: Enable top-level recursive 'autoreconf'

On Thu, Oct 19, 2023 at 6:43 AM Thomas Schwinge wrote: > > Hi! > > On 2023-10-19T11:57:33+0200, Andreas Schwab wrote: > > On Okt 19 2023, Thomas Schwinge wrote: > >> On 2023-10-18T15:42:18+0100, R jd <3246251196r...@gmail.com> wrote: > >>> I guess I can ask, why there is not a recursive approach

Re: Deprecating -fgnu-tm support for GCC 14 and removing it for GCC 15

Personally, since GCC is in stage 3 now, I would push that schedule back a release and move deprecation to GCC 15, and then only remove it for GCC 16 if no one objects, but then again I don't actually use -fgnu-tm myself, so I wouldn't be too upset if the faster schedule is chosen instead. Eric Gallager

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

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

sh from scratch? I'd offer to help with testing but I *just* got a new Intel-based Mac that I haven't even managed to set up yet, so I highly doubt I'll have any money for a new ARM-based Mac anytime soon... Anyways, I'm interested to hear what people are thinking. Thanks, Eric Gallager

Re: Copyright assignment for Rust-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

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.r

Freenode changing ownership

as well? Of course, that would require coming up with a new name for the one being migrated from Freenode, so that it doesn't clash with the existing GCC channel on OFTC... Anyways, just something to consider; let me know if the community decides anything. Thanks, Eric Gallager

Re: Update to GCC copyright assignment policy

in the years since its last release, but regardless of those, are the legal difficulties at least now out of the way? Thanks, Eric Gallager

Re: gcc plugin on MacOS failure

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

deprecations on the changes page ASAP, so that people can have time to prepare for the impending deprecations. Thanks, Eric Gallager

Re: [FYI] bugzilla cleanup

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?

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

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

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

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

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?

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

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

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.cg

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

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?

rogram (deprecated since 2010) is > no longer available. Instead of including the intl sources in your > package, we suggest making the libintl library an optional prerequisite > of your package. This will simplify the build system of your package. > - Accordingly,

Re: remove intl/ directory?

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

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

: gdb has a song: https://www.gnu.org/music/gdb-song.en.html Perhaps GCC could have a song as well? Anyways, just some fun food for thought on this day of foolishness; please don't take these suggestions too seriously (unless you want to). Happy hacking! Eric Gallager

Re: More C type errors by default for GCC 14

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

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

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

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

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

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

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

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

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

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?

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?

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?

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

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

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

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

  1   2   >