On 06/16/2015 07:05 PM, Steve Ellcey wrote:
I have a question about the DRAP register (used for dynamic stack alignment)
and about reserving/using hard registers in general. I am trying to understand
where, if a drap register is allocated, GCC is told not to use it during
general register allo
On Fri, 2015-06-19 at 09:09 -0400, Richard Henderson wrote:
> On 06/16/2015 07:05 PM, Steve Ellcey wrote:
> >
> > I have a question about the DRAP register (used for dynamic stack alignment)
> > and about reserving/using hard registers in general. I am trying to
> > understand
> > where, if a dr
GNU MPFR 3.1.3 ("canard à l'orange", patch level 3), a C library for
multiple-precision floating-point computations with correct rounding,
is now available for download from the MPFR web site:
http://www.mpfr.org/mpfr-3.1.3/
from InriaForge:
https://gforge.inria.fr/projects/mpfr/
and from t
Hello all,
Suppose that I have some header file in C myhead.h, containing notably
// Boehm's garbage collector, notably defines GC_malloc_atomic & GC_malloc
#include
struct myintvec_st {
unsigned vsiz; // allocated size
unsigned vlen; // used length, always <= vsiz
On Sat, 2015-06-20 at 01:56 +0200, Basile Starynkevitch wrote:
> Hello all,
>
> Suppose that I have some header file in C myhead.h, containing notably
>
> // Boehm's garbage collector, notably defines GC_malloc_atomic &
> GC_malloc
> #include
> struct myintvec_st {
>unsig
Consider:
# 1 "dj.c"
# 1 "dj.h" 1 3
int dj(int x);
# 2 "dj.c" 2
int dj(int x)
{
}
If you compile with -g and look at the dwarf output, you see:
<1><2d>: Abbrev Number: 2 (DW_TAG_subprogram)
<2e> DW_AT_external: 1
<2e> DW_AT_name: dj
<31> DW_AT_decl_file : 2
