On 26.11.2022 20:04, Pali Rohár wrote:
> On Monday 21 November 2022 08:24:36 Jan Beulich wrote:
>> But then, with you replying to
>> me specifically, perhaps you're wrongly assuming that I would be
>> planning to look into addressing any or all of these? My earlier reply
>> was merely to point out
On Mon, 28 Nov 2022, 08:08 Jan Beulich via Gcc, wrote:
> On 26.11.2022 20:04, Pali Rohár wrote:
> > On Monday 21 November 2022 08:24:36 Jan Beulich wrote:
> >> But then, with you replying to
> >> me specifically, perhaps you're wrongly assuming that I would be
> >> planning to look into addressin
On 28.11.2022 09:40, Jonathan Wakely wrote:
> On Mon, 28 Nov 2022, 08:08 Jan Beulich via Gcc, wrote:
>
>> On 26.11.2022 20:04, Pali Rohár wrote:
>>> On Monday 21 November 2022 08:24:36 Jan Beulich wrote:
But then, with you replying to
me specifically, perhaps you're wrongly assuming tha
I've got some instrumentation for logging errors to a magic directory,
so that I can see if a build triggered them even when it did not
fail—and hid all compiler errors and warnings.
Unfortunately, some build systems immediately delete the input source
files. Is there some easy way I can dump the
On Mon, Nov 28, 2022 at 12:30 PM Florian Weimer via Gcc wrote:
>
> I've got some instrumentation for logging errors to a magic directory,
> so that I can see if a build triggered them even when it did not
> fail—and hid all compiler errors and warnings.
>
> Unfortunately, some build systems immedi
Hi,
Florian Weimer via Gcc writes:
> Unfortunately, some build systems immediately delete the input source
> files. Is there some easy way I can dump the pre-processed and
> non-preprocessed sources to my log file? I tried to understand how
> -save-temps for crash recovery works, but it seems
* Arsen Arsenović:
> Hi,
>
> Florian Weimer via Gcc writes:
>
>> Unfortunately, some build systems immediately delete the input source
>> files. Is there some easy way I can dump the pre-processed and
>> non-preprocessed sources to my log file? I tried to understand how
>> -save-temps for crash
On Mon, 28 Nov 2022, Florian Weimer via Gcc wrote:
* Arsen Arsenović:
Hi,
Florian Weimer via Gcc writes:
Unfortunately, some build systems immediately delete the input source
files. Is there some easy way I can dump the pre-processed and
non-preprocessed sources to my log file? I tried t
I am part of a team working on a COBOL front end for GCC.
By reverse engineering other front ends, I learned, some months ago, how
to create a function_decl GENERIC node that is the root of a GENERIC tree
describing an entire function.
By calling the routine cgraph_node::finalize_function() wi
Hi Joseph,
On 11/14/22 19:13, Joseph Myers wrote:
On Sun, 13 Nov 2022, Alejandro Colomar via Gcc wrote:
SYNOPSIS:
unary-operator: . identifier
That's not what you mean. See the standard syntax.
Yup; typo there.
unary-expression:
[other alternatives]
unary-operator cast-expressi
Hi Joseph,
On 11/14/22 19:26, Joseph Myers wrote:
On Mon, 14 Nov 2022, Alejandro Colomar via Gcc wrote:
To quote the convenor in WG14 reflector message 18575 (17 Nov
2020) when I asked about its status, "The author asked me not to put those
on the agenda. He will supply updated versions later
On Mon, 2022-11-28 at 15:28 -0600, Robert Dubner wrote:
> I am part of a team working on a COBOL front end for GCC.
>
> By reverse engineering other front ends, I learned, some months ago,
> how
> to create a function_decl GENERIC node that is the root of a GENERIC
> tree
> describing an entire fu
Hi Martin,
On 11/13/22 15:58, Martin Uecker wrote:
Am Sonntag, den 13.11.2022, 15:02 +0100 schrieb Alejandro Colomar:
On 11/13/22 14:33, Alejandro Colomar wrote:
Hi Martin,
On 11/13/22 14:19, Alejandro Colomar wrote:
But there are not only syntactical problems, because
also the type of the
On Tue, 29 Nov 2022, Alex Colomar via Gcc wrote:
> I guess asking the compiler to do two passes on the param list isn't as bad as
> asking to do unbound lookahead. In this case it's bound: look ahead till the
> end of the param list; get as much info as possible, and then do it again to
> comple
Hello,
For class, *I need to come up with a way to improve GCC* and then make a
quick presentation (no implementation required). Ideally, this idea isn't
being worked on already. *I'd appreciate help with coming up with an idea.*
I've thought about this and I'm having trouble coming up with anyt
David, thank you very much. That looks very much like what I was hoping
for.
I'll dig into it tomorrow.
Heartfelt thanks,
Bob Dubner.
-Original Message-
From: David Malcolm
Sent: Monday, November 28, 2022 18:01
To: Robert Dubner ; gcc@gcc.gnu.org
Cc: 'Bob Dubner'
Subject: Re: Code g
I am working on a project which is using an A53 core. The core does not
raise an exception if there is a division by zero (for either integer or
floating point division).
The designers chose to set status bits for the floating point case but not
raise an exception.With the integer divisio
17 matches
Mail list logo
