On Thu, Oct 28, 2021 at 1:26 PM Rasmus Villemoes
wrote:
>
> Hi
>
> I was wondering why the vx_crtbegin.o file had a .init_array section and
> not a .init_array.00101, when the function is defined with
> __attribute__((constructor (101))) (see libgcc/config/vxcrtstuff.c).
>
> After a lot of diggin
On Fri, Oct 29, 2021 at 2:42 AM Bernhard Reutner-Fischer via
Gcc-patches wrote:
>
> From: Bernhard Reutner-Fischer
>
> Bump required DejaGnu version to 1.5.3 (or later).
> Ok for trunk?
OK.
Thanks,
Richard.
> gcc/ChangeLog:
>
> * doc/install.texi: Bump required minimum DejaGnu version.
Hi Michael,
I tried this out on the one POWER machine where I can get something
installed :-) It runs Ubuntu 20.04, but does not appear to have the
right glibc version; it has
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:
I've got a mostly-complete implementation of a faster _Unwind_Find_FDE
implementation which lock-free and async-signal-safe. The core idea is
to turn into effectively this.
const fde *
_Unwind_Find_FDE (void *pc, struct dwarf_eh_bases *bases)
{
struct unw_eh_callback_data data;
cons
hello everyone,
we read chapter 5 and the paper proposed RWTH Aachen University and the
others
They worked on the same project.
some of us will work on OMPD, somebody will work on GDB plugin python
script and somebody will work on GDB support as jakub said ,
but i have some clarifications that migh
On Fri, Oct 29, 2021 at 09:07:38PM +0200, Thomas Koenig wrote:
> Hi Michael,
>
> I tried this out on the one POWER machine where I can get something
> installed :-) It runs Ubuntu 20.04, but does not appear to have the
> right glibc version; it has
>
> $ lsb_release -a
> No LSB modules are availa
Snapshot gcc-10-20211029 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20211029/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
This patch replaces the first patch.
Instead of disallowing long double and only dealing with float128 types, this
patch tries to accommodate the two.
It adds target hooks so the back end can overwrite the kind number for types.
I made the IBM long double type use KIND=15 instead of KIND=16, and
