On Wed, Jun 18, 2025 at 9:14 AM Richard Biener
wrote:
> On Mon, Jun 16, 2025 at 7:06 PM Segher Boessenkool
> wrote:
> >
> > Hi!
> >
> > On Mon, Jun 16, 2025 at 11:41:37AM +0200, Mark Wielaard wrote:
> > > > WaA is decided by the sourceware maintainers. The request form says
> > > > "email addre
On Wed, Jun 11, 2025 at 11:46 AM Segher Boessenkool <
seg...@kernel.crashing.org> wrote:
> On Wed, Jun 04, 2025 at 05:53:18PM -0600, Jeff Law via Gcc wrote:
> > On 6/3/25 1:41 PM, David Edelsohn via Gcc wrote:
> > >What is not working with the current system? What is th
On 10/06/2025 18:43, Christopher Bazley wrote:
Hi David,
On 10/06/2025 14:19, David Brown wrote:
On 10/06/2025 10:43, Jakub Jelinek wrote:
On Tue, Jun 10, 2025 at 09:52:42AM +0200, David Brown via Gcc wrote:
So while correcting the mistakes of the past is either very slow or
impossible, we
On 10/06/2025 10:43, Jakub Jelinek wrote:
On Tue, Jun 10, 2025 at 09:52:42AM +0200, David Brown via Gcc wrote:
So while correcting the mistakes of the past is either very slow or
impossible, we can avoid them in the future. Consistent parameter order
makes code clearer and neater, and should
On 10/06/2025 10:17, LIU Hao wrote:
在 2025-6-10 15:52, David Brown via Gcc 写道:
On 09/06/2025 12:13, Andreas Schwab wrote:
On Jun 09 2025, Chris Bazley via Gcc wrote:
C is a language that allows considerable latitude in where things
are placed:
static int volatile p;
volatile int
uture. Consistent parameter order
makes code clearer and neater, and should be encouraged.
David
On Wed, Jun 4, 2025 at 5:24 AM Richard Earnshaw (lists) <
richard.earns...@arm.com> wrote:
> On 03/06/2025 20:41, David Edelsohn via Gcc wrote:
> > On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford <
> richard.sandif...@arm.com>
> > wrote:
> >
> >> Davi
On Tue, Jun 3, 2025 at 3:23 PM Richard Sandiford
wrote:
> David Edelsohn writes:
> > On Tue, Jun 3, 2025 at 6:22 AM Richard Sandiford via Gcc <
> gcc@gcc.gnu.org>
> > wrote:
> >
> >> Hi,
> >>
> >> At the moment, all reviewers and mainta
e to ask the SC instead.
>
> In case it sounds otherwise, I'm really not trying to pick a fight here.
> I just don't remember this being discussed on-list for a long time,
> so it seemed worth bringing up. (Maybe it has been discussed at the
> Cauldron -- not sure.)
>
What is a request to the GCC SC preventing?
The GCC SC already requests the opinion of existing reviewers and
maintainers.
David
>
> Thanks,
> Richard
>
ngements and code eliminations, and
flushes any data held in registers. Small local variables, such as loop
indices, will be unaffected.
None of this gives an answer as to whether gcc is generating code that
accesses memory efficiently or not. But it might help you get a clearer
picture, and that in turn might help the gcc developers find weak spots
in the compiler that can be improved.
David
Please ignore this message.
Dave
--
John David Anglin dave.ang...@bell.net
On Sun, 2025-03-23 at 09:21 +0530, mannem navyasree via Gcc wrote:
> Hi, I’m Navya sree mannem , new to GCC. I’d like to learn how to
> contribute, maybe in improving GCC’s optimization passes to make
> compiled
> code faster. Can anyone suggest a starting point or mentor me?”
Hi!
Thanks for your
On Mon, 2025-02-10 at 09:29 +, Jonathan Wakely via Gcc wrote:
> On Sun, 9 Feb 2025, 09:08 Thomas Koenig via Gcc,
> wrote:
>
> > Hello world,
> >
> > looking at a few Fortran bug reports, I found some cases where
> > it was not clear if the program in question was standard-conforming
> > or n
On Mon, 2025-02-03 at 11:24 +0100, Mark Wielaard wrote:
> Hi Tuur,
>
> On Mon, Feb 03, 2025 at 09:46:37AM +, JohnyTheCarrot via Gcc
> wrote:
> > I'm in the process of writing my own C compiler for educational
> > purposes.
> > To this end, I have decided to integrate into my compiler my own
>
On Mon, 2025-02-03 at 11:49 +0100, Basile Starynkevitch wrote:
> >
> >
> > I'm in the process of writing my own C compiler for educational
> > purposes.
>
>
> Then look also into https://frama-c.com/ and
> https://github.com/bstarynk/bismon
> and https://nwcc.sourceforge.net/ and https://bellar
On Mon, 2025-02-03 at 09:46 +, JohnyTheCarrot via Gcc wrote:
> Dear GCC Developers,
Hi Tuur
>
> I'm in the process of writing my own C compiler for educational
> purposes.
> To this end, I have decided to integrate into my compiler my own C++
> port ( https://github.com/johnythecarrot/mjolni
On 31/01/2025 14:22, noname noname via Gcc wrote:
hello, I'm a regular user of Fedora 41 Workstation. I usually install all
my apps through one command which has tons of packages to it. So I'm not
sure which one of them pulled gcc as a dependency. But either way. While
installing all of them, dnf
On 31/01/2025 14:22, noname noname via Gcc wrote:
hello, I'm a regular user of Fedora 41 Workstation. I usually install all
my apps through one command which has tons of packages to it. So I'm not
sure which one of them pulled gcc as a dependency. But either way. While
installing all of them, dnf
On Thu, 2025-01-30 at 09:03 +, Jonathan Wakely via Gcc wrote:
> On Thu, 30 Jan 2025, 09:00 Dmitry Antipov,
> wrote:
>
> > With (probably) -Wmaybe-uninitialized and/or -Wextra, shouldn't the
> > compiler emit
> > warning about possibly uninitialized 'y' passed to 'ddd()' in the
> > example
> >
On Sat, 2025-01-11 at 12:32 -0500, David Malcolm wrote:
> On Fri, 2025-01-10 at 15:52 -0500, James K. Lowden wrote:
> > What should I do with the following message?
> >
> > cobol1: warning: depth l
On Fri, 2025-01-10 at 15:52 -0500, James K. Lowden wrote:
> What should I do with the following message?
>
> cobol1: warning: depth line copybook filename
> -
>
> cobol1: warning: 1 1 prog.cob
> cobol1: warning:
On 01/12/2024 23:55, Frederick Virchanza Gotham via Gcc wrote:
Some modern CPU's now have control flow enforcement. Here's how it
works on Intel CPU's:
"The shadow stack stores a copy of the return address of each CALL. On
a RET, the processor checks if the return address stored in the normal
st
tests.
But that was using gcc13 to build gcc13.
Then my debian system updated to gcc14 and it is failing much quicker.
I will try to post the build errors shortly.
Again thx
On Sat, 2024-11-30 at 09:54 +, Jonathan Wakely wrote:
>
>
> On Sat, 30 Nov 2024, 09:01 David H.
Is it possible to build gcc 13 with gcc 14 ?
My system updated to gcc 14 and I am doing some private development for
hardware stesting of a new memory addressing paradigm using the GCC 13
code base.
Now I can't compile.
Do I need to revert my base compiler to gcc 13 ?
On Thu, 2024-11-28 at 03:56 +, Sam James wrote:
> David Malcolm via Gcc writes:
>
> > I merged libdiagnostics to GCC trunk on Monday:
> > https://gcc.gnu.org/wiki/libdiagnostics
> >
> > Unfortunately I've since discovered there's at least one
>
On 28/11/2024 12:18, Aaron Peter Bachmann via Gcc wrote:
Two suggestions for GCC beginners projects
I watched some of the 2024 Gnu Cauldron videos. The question of what
could be a suitable project for a beginner came up. I have two suggestions:
1. Add a warning when users use reserved or p
On Thu, 2024-11-21 at 08:08 +0200, Eli Zaretskii wrote:
> > Date: Wed, 20 Nov 2024 16:11:16 -0500
> > From: David Malcolm via Gcc
> >
> > I merged libdiagnostics to GCC trunk on Monday:
> > https://gcc.gnu.org/wiki/libdiagnostics
> >
> > Unfortunat
I merged libdiagnostics to GCC trunk on Monday:
https://gcc.gnu.org/wiki/libdiagnostics
Unfortunately I've since discovered there's at least one libdiagnostics
.so already in Debian:
https://tracker.debian.org/pkg/diagnostics
https://packages.debian.org/search?searchon=contents&keywords=libdiag&
On 13/11/2024 22:34, James K. Lowden wrote:
On Thu, 14 Nov 2024 10:04:59 +0100
David Brown via Gcc wrote:
No. This is - or at least appears to be - missing critical thinking.
You are explaining this to someone who designed research databases and
who implemented quantitative models that ran
On 12/11/2024 22:44, James K. Lowden wrote:
On Tue, 12 Nov 2024 18:12:50 +0100
David Brown via Gcc wrote:
Under what circumstances would you have code that :
...
d) Would be perfectly happy with "x" having the value 2.225e-307 (or
perhaps a little larger) and doing the division
On Tue, 2024-11-12 at 16:54 -0500, Aravind Ceyardass via Gcc wrote:
> Hello all,
>
> I have implemented a GCC plugin that instruments code to implement
> reference counted memory management instead of manually adding calls
> to inc()/dec() reference counts. It is a work in progress. Any
> ideas/su
On 12/11/2024 15:29, Sad Clouds via Gcc wrote:
On Mon, 11 Nov 2024 21:14:43 + (UTC)
Joseph Myers wrote:
I don't think this has anything to do with whether one operand of the
comparison is a constant. It's still the case when comparing with 0.0
that it's OK if your algorithm is designed su
er or an "aligned" attribute). Secondly, it
would add another ".align" command at the end of the section so that if
a section with a small alignment specifier is linked after one with a
specified large alignment, you'll get padding inserted.
mvh.,
David
On Mon, 2024-10-21 at 03:22 +0200, 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 you
I am pleased to announce that the GCC Steering Committee has
appointed Stefan Schulze Frielinghaus as a s390x port co-maintainer.
Please join me in congratulating Stefan on his new role. Stefan, please
update your listing in the MAINTAINERS file.
Cheers!
David
icrocross, you might have
luck with someone from Code Sourcery. I believe they were doing a lot
of the work on ARM gcc on behalf of microcontroller manufacturers at
that time.
David
On 23/09/2024 22:09, Andrew Pinski via Gcc wrote:
While working on the review from
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/663418.html .
I noticed that there are places which use `side effects` and some use
`side-effects`. I assume we should follow a similar pattern as
`back-end`
On Mon, 2024-09-23 at 15:45 -0700, Bryon Quackenbush via Gcc wrote:
> Greetings all,
>
> I am just starting the fun process of getting familiar with the
> GCC
> compiler and all it's various components (I'm starting out with
> LIBCPP,
> since that seems relatively small and simple)..
Welcome!
On Sun, 2024-09-15 at 15:20 +0330, Ghorban M. Tavakoly via Gcc wrote:
> Hi
>
> On Sun, Sep 15, 2024 at 11:59 AM Jan Hubicka wrote:
>
> > > On Sat, Sep 14, 2024 at 1:17 PM Ghorban M. Tavakoly via Gcc
> > > wrote:
> > > >
> > > > > > Is there any change to have some LTO progress indicator
> > >
On Mon, Sep 16, 2024 at 9:40 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> - Am 16. Sep 2024 um 15:24 schrieb David Edelsohn dje@gmail.com:
>
> > On Mon, Sep 16, 2024 at 9:15 AM Sebastian Huber <
> > sebastian.hu...@embedded-brain
On Mon, Sep 16, 2024 at 9:15 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> - Am 16. Sep 2024 um 15:02 schrieb David Edelsohn dje@gmail.com:
>
> > On Sun, Sep 15, 2024 at 7:29 PM Sebastian Huber <
> > sebastian.hu...@embedded-brain
person weeks, months, years?
>
Why do you wish to resurrect the port?
Thanks, David
>
> Kind regard, Sebastian
>
> --
> embedded brains GmbH & Co. KG
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.hu...@embe
On Fri, 2024-09-06 at 08:44 -0400, Ben Boeckel via Gcc wrote:
> On Tue, Sep 03, 2024 at 16:53:43 +0100, Iain Sandoe wrote:
> > I think that might be a misunderstanding on the part of the author;
> > AFAIU both GCC and MSVC _do_ require access to the sources at BMI
> > consume-time to give decent di
I've been debugging a use-immediately-after-free bug involving obstacks
(the bug isn't in trunk; I found it whilst testing one of my patches).
It was only visible as a crash when it happened that the call to
obstack_free led to the underlying buffer being freed. Most of the
time, the bug was dorm
On Wed, 2024-07-24 at 02:59 -0500, Thor Preimesberger via Gcc wrote:
> Sure - we actually already emit json in optinfo-emit-json.cc, and
> there
> are implementations of json and pretty-printing/dumping it out also.
> I got
> a hacky version of our current raw dump working with json objects,
> but
On Mon, 2024-07-22 at 17:54 +0100, Joern Wolfgang Rennecke wrote:
>
>
> On 22/07/2024 17:13, Joern Wolfgang Rennecke wrote:
> > I guess you could reduce the differences between platforms if you
> didn't
> > use types as defined by headerfiles directly, as they might be
> > #defines
> > or type
On Mon, 2024-07-22 at 17:13 +0100, Joern Wolfgang Rennecke wrote:
>
>
> On 22/07/2024 16:44, David Malcolm wrote:
> > Does it help to hack this change into prune.exp:
> >
> > diff --git a/gcc/testsuite/lib/prune.exp
> > b/gcc/testsuite/lib/prune.exp
> >
On Mon, 2024-07-22 at 11:37 +0100, Joern Wolfgang Rennecke wrote:
> While on x86_64-pc-linux-gnu, the second diagram shows the type
> written
> as 'int', as expected, on a 16 and 32 bit newlib based toolchain, it
> is
> being output as int32_t . And all the formatting is also a bit
> different,
] [[gnu::nonnull]]
[[gnu::null_terminated_string_arg]] const_cstring;
David
On Mon, 2024-07-08 at 17:01 +0200, Alejandro Colomar wrote:
> On Mon, Jul 08, 2024 at 10:30:48AM GMT, David Malcolm wrote:
> > > > Why is this change worth
> > > > making? Real-world programs do not make calls like that.
> > >
> > > Because it makes
On Sun, 2024-07-07 at 14:42 +0200, Alejandro Colomar wrote:
> Hi Paul,
>
> On Sun, Jul 07, 2024 at 12:42:51PM GMT, Paul Eggert wrote:
> > On 7/7/24 03:58, Alejandro Colomar wrote:
> >
> > > I've incorporated feedback, and here's a new revision, let's call
> > > it
> > > v0.2, of the draft for a W
On Tue, 2024-07-02 at 22:39 +0200, Mark Wielaard wrote:
> Hi David,
>
> On Tue, Jul 02, 2024 at 03:57:58PM -0400, David Malcolm wrote:
> > > > At -O0 sure, that is how __builtin_constant_p works.
> > > > The above is intended for optimized compilation, and I thin
On Tue, 2024-07-02 at 21:21 +0200, Florian Weimer wrote:
> * Jakub Jelinek:
>
> > On Tue, Jul 02, 2024 at 12:54:09PM -0400, David Malcolm via Gcc
> > wrote:
> > > Back in 2007 glibc gained some logic to implement "error" and
> > > "error_at_li
On Tue, 2024-07-02 at 19:02 +0200, Jakub Jelinek wrote:
> On Tue, Jul 02, 2024 at 12:54:09PM -0400, David Malcolm via Gcc
> wrote:
> > Back in 2007 glibc gained some logic to implement "error" and
> > "error_at_line" by splitting into zero and non-zero case
Back in 2007 glibc gained some logic to implement "error" and
"error_at_line" by splitting into zero and non-zero cases, with the
nonzero case calling a "noreturn" function [1].
This doesn't seem to work. I tested back to 4.8.1 with Compiler
Explorer [2], which seems to be the earliest GCC that su
On Fri, 2024-06-21 at 18:46 -0400, Eric Gallager wrote:
> 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 "SAR
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).
Dave
plying aix_null to wchar.h
Applying stdio_va_list_clientsto wchar.h
Fixed: wchar.h
Fixing directory /usr/include/X11 into
/tmp/GCC/gcc/include-fixed/root/usr/lpp/X11/include/X11
Applying io_quotes_defto X11/Xmu/Atoms.h
Laugh or cry.
David
On 04/06/2024 19:43, Michael Matz via Gcc wrote:
Hello,
On Tue, 4 Jun 2024, Richard Biener wrote:
A pragmatic solution might be a new target hook, indicating a specified
builtin is not to be folded into an open-coded form.
Well, that's what the mechanism behind -fno-builtin-foobar is suppose
ls are put in the common section, the compiler does not
know their relative position until link time. But if they are in bss or
data sections (with or without -fdata-sections), it can at least use
anchors to access data in the translation unit that defines the data
objects.
David
Thanks,
And
Please choose whichever procedure works best for the needs of you and any
organizational affiliation.
Thanks, David
On Sat, May 25, 2024 at 6:37 AM Seyed Sajad Kahani via Gcc
wrote:
> Hi,
>
> I am writing to request the FSF copyright assignment forms, as they
> are a legal req
On Tue, 2024-04-30 at 21:15 +0200, Richard Biener via Gcc wrote:
>
>
> > Am 30.04.2024 um 21:11 schrieb Jason Merrill via Gcc
> > :
> >
> > On Fri, Apr 26, 2024 at 5:44 AM Aldy Hernandez via Gcc
> > wrote:
> > >
> > > In implementing prange (pointer ranges), I have found a 1.74%
> > > slowdow
On Tue, 2024-04-02 at 10:06 -0400, David Malcolm wrote:
> What timezone are you in? (I'm in EDT, UTC+4)
Sorry, that should be UTC-4 (on the east coast of the US)
Dave
On Sat, 2024-03-30 at 13:54 +0200, Nada Elsayed wrote:
> I think that I didn't fully understand the project, so I read more
> and
> updated the Timeline Suggestion.
Hi Nada
I'm very sorry for not responding sooner; I've been dealing with an
difficult issue that's arisen outside of my computer wo
On 18/03/2024 16:00, Martin Uecker via Gcc wrote:
Am Montag, dem 18.03.2024 um 14:29 +0100 schrieb David Brown:
On 18/03/2024 12:41, Martin Uecker wrote:
Hi David,
Am Montag, dem 18.03.2024 um 10:00 +0100 schrieb David Brown:
Hi,
I would very glad to see this change in the standards
On 18/03/2024 17:46, David Brown via Gcc wrote:
On 18/03/2024 14:54, Andreas Schwab via Gcc wrote:
On Mär 18 2024, David Brown wrote:
I think it would be possible to have an implementation where "signed
char" was 8-bit two's complement except that 0x80 would be a trap
repres
On 18/03/2024 14:54, Andreas Schwab via Gcc wrote:
On Mär 18 2024, David Brown wrote:
I think it would be possible to have an implementation where "signed
char" was 8-bit two's complement except that 0x80 would be a trap
representation rather than -128.
signed char cannot ha
On 18/03/2024 12:41, Martin Uecker wrote:
Hi David,
Am Montag, dem 18.03.2024 um 10:00 +0100 schrieb David Brown:
Hi,
I would very glad to see this change in the standards.
Should "byte type" include all character types (signed, unsigned and
plain), or should it be res
ype-based alias analysis
and thus view all types as "byte types" in this way. For gcc, there
could be a kind of reverse "may_alias" type attribute to create such types.
There are a number of other features that could make allocation
functions more efficient and safer in use, and
On Thu, 2024-03-14 at 13:28 +, Jonathan Wakely via Gcc wrote:
> On Thu, 14 Mar 2024 at 12:54, Pierrick Philippe
> wrote:
> >
> > Hi all,
Hi Pierrick! It was good to meet you at FOSDEM.
> >
> > I was wondering, is there any conventions or guidelines regarding
> > the
> > usage of types and
On Tue, 2024-02-27 at 10:15 +0100, Richard Biener via Gcc wrote:
> On Fri, Feb 23, 2024 at 10:22 AM Miro Palmu via Gcc
> wrote:
> >
> > Hi.
> >
> > I have a idea about long term hobby project relating to gcc,
> > so with this email I'm asking feedback about the idea
> > early rather than later.
The ICE in PR analyzer/111441 is due to this assertion in
fold_binary_loc failing:
11722 gcc_assert (TYPE_PRECISION (atype) == TYPE_PRECISION
(type));
where code=MULT_EXPR, type=, and:
(gdb) p type
$1 =
(gdb) p atype
$2 =
due to the analyzer building a mult_expr node with tho
On Tue, 2024-02-13 at 23:40 -0800, Andi Kleen via Gcc wrote:
> Robert Dubner writes:
>
> > There didn't seem to be any such functionality in GCC. I found a
> > routine
> > in print-tree.cc which printed out a single node, but I needed to
> > understand the entire tree of nodes for a function.
>
On 12/02/2024 17:47, Hugh Gleaves via Gcc wrote:
I’m interested in whether it would be feasible to add an optimization that
compacted assignments to multiple bit fields.
Today, if I have a 32 bit long struct composed of say, four 8 bit fields and
assign constants to them like this:
em as suck? Or
are they real failures of the analyzer?
see also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113150
Although I xfail'ed the tests on HPUX, I left the bug open.
Dave
--
John David Anglin dave.ang...@bell.net
On Fri, Jan 26, 2024 at 3:40 PM NightStrike via Gcc wrote:
>
> On Thu, Jan 25, 2024, 11:27 Iain Sandoe wrote:
>
> > E.g. with Ada it is possible to port to a new platform by first building a
> > cross-compiler and then to use that cross-compiler to build a “native
> > cross” (build != host == tar
On Wed, 2024-01-17 at 17:52 -0500, David Malcolm wrote:
> On Tue, 2024-01-16 at 15:44 +0100, Pierrick Philippe wrote:
> > Hi David, hi all,
>
> Hi Pierrick.
>
> >
> > I was playing along with APIs from the Static Analyzer and
> > encountered a
> > segf
volunteer
> to
> be the main org-admin for GCC again but let me know if you think I
> shouldn't or that someone else should or if you want to do it
> instead.
> Otherwise I'll assume that I will and I hope that I can continue to
> rely
> on David Edelsohn and Thomas S
On Tue, 2024-01-16 at 15:44 +0100, Pierrick Philippe wrote:
> Hi David, hi all,
Hi Pierrick.
>
> I was playing along with APIs from the Static Analyzer and
> encountered a
> segfault in gcc/tree.cc:5068 (i.e. in function build2 and failure is
> due
> to a
> gcc_asser
On Wed, 2023-12-20 at 11:16 -0800, Eric Batchelor wrote:
> Hello, I unintentionally stumbled upon some strange behaviour that
> occurred due to a typo.
> I reproduced the behaviour where an object (std::string in my case)
> can
> be passed to a function by reference, uninitialized, WITHOUT a
> co
implimenting that is a future problem.
On Mon, 2023-12-18 at 08:59 +0100, Richard Biener wrote:
> On Sat, Dec 16, 2023 at 11:53 PM Jonathan Wakely via Gcc
> wrote:
> >
> > On Sat, 16 Dec 2023 at 22:41, David H. Lynch Jr. wrote:
> > > I am looking for any help I can ge
ler.
Next the code generated for get/put will be different.
On Mon, 2023-12-18 at 08:59 +0100, Richard Biener via Gcc wrote:
> On Sat, Dec 16, 2023 at 11:53 PM Jonathan Wakely via Gcc
> wrote:
> >
> > On Sat, 16 Dec 2023 at 22:41, David H. Lynch Jr. wrote:
>
On Thu, 2023-12-14 at 20:50 -0500, James K. Lowden wrote:
> On Fri, 15 Dec 2023 14:43:22 -0500
> "David H. Lynch Jr. via Gcc" wrote:
>
> > Right now I am just focused on some means to deliver support.
>
> Hi David,
>
> My colleague Bob Dubner and I have b
I am part of a project developing content addressable memory. I am the
2nd author for a paper on this presented at MEMSYS 2023, and with
additions likely to be accepted by ACM shortly.
https://www.memsys.io/wp-content/uploads/2023/09/10.pdf
My role is to develop software to demonstrate the benef
it to the gcc-help list.
Then people can try it and give opinions - maybe there is a gcc bug.
I hope that all helps.
David
On 11/12/2023 18:14, Jingwen Wu via Gcc wrote:
Hello, I'm sorry to bother you. And I have some gcc compiler optimization
questions to ask you.
First of all, I used cs
On Mon, 2023-12-04 at 10:09 -0500, Stan Srednyak wrote:
> Hi David, thanks for your email. I really appreciate it.
>
> Your notes are certainly of help, but I also had a specific question:
> how
> to access the trees as they are being constructed by the front end.
> Do you
&
On Sat, 2023-12-02 at 17:41 -0500, Stan Srednyak via Gcc wrote:
> Dear GCC community,
>
> I am assigned the task to debug the trees as being produced by the
> cp_parser. I was able to print some of the trees using the
> debug_tree()
> function. But I am still confused as to where is the tree objec
uld be happy to try to sponsor you and other documentation
writers through the Google Season of Docs program.
Thanks, David
the
room that hosted the second track of the conference.
Thanks, David
status.html
@@ -1418,7 +1418,7 @@
C++14 Support in GCC
- GCC has full support for the of the 2014 C++ standard.
+ GCC has full support for the 2014 C++ standard.
This mode is the default in GCC 6.1 up until GCC 10 (inclusive); it can
be explicitly selected with the -std=c++14 command-l
tion about this devroom, please send a message to
gcc-devroom-manager at fosdem dot org.
Organizers of the devroom can also be reached on IRC at
irc://irc.oftc.net/#gcc; see https://gcc.gnu.org/wiki/GCConIRC
### Program Committee
* David Malcolm (dmalcolm at redhat dot com)
* Thomas Schwinge (tschwinge at googlemail dot com)
t; will be made a typedef as
a GCC extension.
But if there are problems with the interaction between pre-processor
macros and the formatting of diagnostic messages, then that is
definitely something that you should file as a bug report and which can
hopefully be fixed.
David
On Fri, 2023-10-27 at 12:48 -0700, Andrew Pinski wrote:
> Hi David and others,
> I am in the process of improving phi-opt and moving what was
> handled
> in value_replacement to match-and-simplify and ran into a few
> failures
> in the analyzer testsuite.
> For an example
On Mon, 2023-10-23 at 11:24 -0400, Jason Merrill wrote:
> On 10/23/23 11:16, David Malcolm wrote:
> > On Wed, Jan 25, 2023 at 4:09 PM Ben Boeckel via Gcc
> > wrote:
> > >
> > > This simplifies the interface for other UTF-8 validity detections
> > > w
On Wed, Jan 25, 2023 at 4:09 PM Ben Boeckel via Gcc wrote:
>
> This simplifies the interface for other UTF-8 validity detections when a
> simple "yes" or "no" answer is sufficient.
>
> libcpp/
>
> * charset.cc: Add `_cpp_valid_utf8_str` which determines whether
> a C string is vali
On Tue, 2023-10-03 at 14:37 +0200, Dodji Seketeli wrote:
> Good day fine fellows!
>
> [...]
>
> Mark Wielaard a écrit:
>
> > Also Dodji, Jose and Gwen (on CC) are trying to coordinate a Fosdem
> > devroom for the various projects. Please contact them if you want
> > to
> > help out with that.
>
On 11/10/2023 12:17, Florian Weimer wrote:
* David Brown:
On 11/10/2023 10:10, Florian Weimer wrote:
* David Brown:
So IMHO (and as I am not a code contributor to GCC, my opinion really
is humble) it is better to be stricter than permissive, even in old
standards. It is particularly
On 11/10/2023 10:10, Florian Weimer wrote:
* David Brown:
So IMHO (and as I am not a code contributor to GCC, my opinion really
is humble) it is better to be stricter than permissive, even in old
standards. It is particularly important for "-std=c89", while
"-std=gnu89&quo
it is helpful to you to hear
other opinions here, especially about small-systems embedded
programming, at least in my own experience.
David
1 - 100 of 2075 matches
Mail list logo
