Eric Botcazou writes:
>> Output of -fstack-usage is not accurate
>> ===
>>
>> This article mentions a "call cost":
>> https://mcuoneclipse.com/2015/08/21/gnu-static-stack-usage-analysis/
>>
>> I checked for myself, by looking at the change of the stackpointer
I have a vision. It is gcc/gcc/incpath.c that the problem is in.
I had been looking through that file for a few days but eventually gave up.
It is worth mentioning that adding an '-iprefix /this/need/not/exist' vanishes
the problem.
This might have something to do with the following line in incpa
We use neither --with-sysroot nor --with-build-sysroot.
The reason is that, the hard-coded path in GCC repository - that is, the
/mingw/ one - does not actually exist.
In order to build GCC for mingw targets, we take either solution:
0) Make a symlink (or rather, a copy, since Windows does not su
> Output of -fstack-usage is not accurate
> ===
>
> This article mentions a "call cost":
> https://mcuoneclipse.com/2015/08/21/gnu-static-stack-usage-analysis/
>
> I checked for myself, by looking at the change of the stackpointer with a
> debugger, and, yes, t
On Mon, 9 May 2016, Michael Matz wrote:
> Sure. Same QoI bug in my book. (And I'm not motivated enough to find out
> if the various C standards weren't just following POSIX whe setjmp was
> included, or really the other way around).
Standards for setjmp and longjmp date back at least as far a
Hi,
sorry for reopening a very old thread, it took some time until I got around to
write a script that parses the output of -fdump-ipa-cgraph and -fstack-usage.
I'm using gcc 5.3 currently.
It's mostly what I need, I get all the information about the callgraph that I
wanted to get (what's inline
Hi,
On Mon, 9 May 2016, Rich Felker wrote:
> > Done. I never understood why they left in the hugely unuseful
> > {sig,}{set,long}jmp() but removed the actually useful *context()
> > (amended somehow like above).
>
> Because those are actually part of the C language
Sure. Same QoI bug in my
On Mon, May 9, 2016 at 2:03 PM, Joel Sherrill wrote:
>
> On 5/9/2016 3:41 PM, Ian Lance Taylor wrote:
>>
>> On Mon, May 9, 2016 at 1:07 PM, Joel Sherrill
>> wrote:
>>>
>>>
>>> One complication on RTEMS which is a single process, multi-threaded RTOS
>>> is that we can no longer check the stack bou
On Mon, May 9, 2016 at 1:31 PM, Brett Neumeier wrote:
> On Tue, May 3, 2016 at 10:01 AM, lh_mouse wrote:
>> Should I file a bug report then?
>> We need some Linux testers, though not many people on Linux relocate
>> compilers.
>
> For what it's worth -- I encountered the same problem on a GNU/Li
On Mon, 9 May 2016, David Wohlferd wrote:
> In my defense, I can't find any official list of which are 'tertiary' and
> which are deprecated (https://gcc.gnu.org/ml/gcc/2016-03/msg00010.html).
Deprecated targets are exactly those in the "# Obsolete configurations."
list in config.gcc (targets re
On 5/9/2016 3:41 PM, Ian Lance Taylor wrote:
On Mon, May 9, 2016 at 1:07 PM, Joel Sherrill wrote:
One complication on RTEMS which is a single process, multi-threaded RTOS
is that we can no longer check the stack bounds. For threads, we know
where the stack memory is and the range for each th
On 5/9/2016 6:42 AM, paul_kon...@dell.com wrote:
On May 8, 2016, at 6:27 PM, David Wohlferd wrote:
If these architectures aren't supported anymore, is it time to drop some of
these from this page?
Your theory is quite mistaken. A lot of the ones you labeled "drop" are
supported. Quite poss
On Mon, May 09, 2016 at 10:03:02PM +0200, Michael Matz wrote:
> Hi,
>
> On Mon, 9 May 2016, Rich Felker wrote:
>
> > > > The *context APIs are deprecated and I'm not sure they're worth
> > > > supporting with this. It would be a good excuse to get people to
> > > > stop using them.
> > >
> > >
On Mon, May 9, 2016 at 1:07 PM, Joel Sherrill wrote:
>
> One complication on RTEMS which is a single process, multi-threaded RTOS
> is that we can no longer check the stack bounds. For threads, we know
> where the stack memory is and the range for each thread. For ucontext_t,
> it seems this knowl
On Tue, May 3, 2016 at 10:01 AM, lh_mouse wrote:
> Should I file a bug report then?
> We need some Linux testers, though not many people on Linux relocate
> compilers.
For what it's worth -- I encountered the same problem on a GNU/Linux
system. In my specific situation, I'm cross-compiling GCC u
On 5/9/2016 3:03 PM, Michael Matz wrote:
Hi,
On Mon, 9 May 2016, Rich Felker wrote:
The *context APIs are deprecated and I'm not sure they're worth
supporting with this. It would be a good excuse to get people to
stop using them.
How? POSIX decided to remove the facilities without any ade
On 5/9/2016 2:45 PM, Ian Lance Taylor wrote:
On Mon, May 9, 2016 at 12:41 PM, Joel Sherrill
wrote:
On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
The *context APIs are deprecated and I'm not sure they're worth
supporting with this. It w
Hi,
On Mon, 9 May 2016, Rich Felker wrote:
> > > The *context APIs are deprecated and I'm not sure they're worth
> > > supporting with this. It would be a good excuse to get people to
> > > stop using them.
> >
> > How? POSIX decided to remove the facilities without any adequate
> > replacem
On Mon, May 9, 2016 at 12:48 PM, Joel Sherrill
wrote:
>
> On 5/9/2016 2:45 PM, Ian Lance Taylor wrote:
>>
>> On Mon, May 9, 2016 at 12:41 PM, Joel Sherrill
>> wrote:
>>>
>>>
>>> On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
>
On Mon, May 9, 2016 at 12:41 PM, Joel Sherrill
wrote:
>
> On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
>>
>> On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
>>>
>>>
>>> The *context APIs are deprecated and I'm not sure they're worth
>>> supporting with this. It would be a good excuse to get p
On Mon, May 9, 2016 at 12:35 PM, Rich Felker wrote:
> On Mon, May 09, 2016 at 09:02:33PM +0200, Michael Matz wrote:
>> Hi,
>>
>> On Sat, 7 May 2016, Rich Felker wrote:
>>
>> > > > * sigaltstack and swapcontext are broken too.
>> > >
>> > > We have prototype that supports swapcontext that we're hap
On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
The *context APIs are deprecated and I'm not sure they're worth
supporting with this. It would be a good excuse to get people to stop
using them.
The gccgo library uses them, because there is n
On Mon, May 9, 2016 at 5:18 AM, Jonathan Wakely wrote:
> On 8 May 2016 at 02:10, Christopher Di Bella wrote:
>> Hi all,
>>
>> I've been tracking gcc-digest for a bit, but would like to be a little
>> more involved in the development of gcc.
>>
>> I haven't been able to find anything about the CppC
On Mon, May 09, 2016 at 09:02:33PM +0200, Michael Matz wrote:
> Hi,
>
> On Sat, 7 May 2016, Rich Felker wrote:
>
> > > > * sigaltstack and swapcontext are broken too.
> > >
> > > We have prototype that supports swapcontext that we're happy to
> > > release, but it clearly requires more work bef
On Fri, May 6, 2016 at 10:42 PM, Rich Felker wrote:
>
> The *context APIs are deprecated and I'm not sure they're worth
> supporting with this. It would be a good excuse to get people to stop
> using them.
The gccgo library uses them, because there is no working alternative.
In general coroutine
Hi,
On Sat, 7 May 2016, Rich Felker wrote:
> > > * sigaltstack and swapcontext are broken too.
> >
> > We have prototype that supports swapcontext that we're happy to
> > release, but it clearly requires more work before being ready to merge
> > upstream.
>
> The *context APIs are deprecated
On 05/06/2016 09:28 PM, Woon yung Liu wrote:
Regarding multiplication of vectors, is there a way to work with a
multiplication operation that results in something like this (the result is
spread across these 3 registers), without re-ordering any elements:
RD: A6xB6, A4xB4, A2xB2, A0xA0
LO: A7
On 08/05/16 23:13, Oleg Endo wrote:
There are nearly 10,000 still unresolved bugs in Bugzilla, almost
half of which are New, and a third Unconfirmed, so I'm sure any
effort to help reduce the number is of value and appreciated.
That's exactly what prompted me to ask. There's such a vast number
Hey,
I wanted to introduce myself to the gcc’s developer's community.
I have been selected for the google summer of code program with gcc for 2016.
The title of my project is - Replace libiberty with gnulib
I’ve created a very short wiki describing the project and my initial approach
at how I’ll
> On May 8, 2016, at 6:27 PM, David Wohlferd wrote:
>
> Looking at the v6 release criteria (https://gcc.gnu.org/gcc-6/criteria.html)
> there are about a dozen supported platforms.
>
> Looking at the Machine Constraints docs
> (https://gcc.gnu.org/onlinedocs/gcc/Machine-Constraints.html), ther
On 05/08/2016 04:13 PM, Oleg Endo wrote:
Sometimes there is. Before randomly closing any bugs because they are
too old, one should at least have a look at them and see if they're
still an issue etc. Often things would've been fixed along the way,
but not all of them.
When this is the case I do
On 05/08/2016 04:03 PM, David Wohlferd wrote:
On 4/28/2016 9:41 AM, Martin Sebor wrote:
On 04/28/2016 01:35 AM, David Wohlferd wrote:
As part of the work I've done on inline asm, I've been looking thru the
bugs for it. There appear to be a number that have been fixed or
overtaken by events ove
On 8 May 2016 at 02:10, Christopher Di Bella wrote:
> Hi all,
>
> I've been tracking gcc-digest for a bit, but would like to be a little
> more involved in the development of gcc.
>
> I haven't been able to find anything about the CppCoreGuidelines in
> gcc -- I'm wondering if there's a warning sys
33 matches
Mail list logo
