From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: GDB 10 branching - 2020-06-27 Update
Date: Fri, 3 Jul 2020 14:07:08 +0100 [thread overview]
Message-ID: <20200703130708.GV2737@embecosm.com> (raw)
In-Reply-To: <d7657c0b-9c20-fd5f-a164-389037d8fcdb@embedded-brains.de>
* Sebastian Huber <sebastian.huber@embedded-brains.de> [2020-07-03 10:15:51 +0200]:
> Hello,
>
> On 27/06/2020 17:40, Joel Brobecker wrote:
> > Not Critical, but Requested:
> > ----------------------------
> >
> > <none>
>
> it would be nice to have a fix for linker errors with GCC 10 (-fno-common
> default):
>
> https://sourceware.org/pipermail/gdb-patches/2020-July/170083.html
>
> https://sourceware.org/pipermail/gdb-patches/2020-July/170084.html
I'll try to get these reviewed today or over the weekend.
Thanks,
Andrew
>
> I built GDB for the following targets recently with GCC 10:
>
> * aarch64-rtems
> * arm-rtems
> * bfin-rtems
> * i386-rtems
> * lm32-rtems
> * m68k-rtems
> * microblaze-rtems
> * mips-rtems
> * moxie-rtems
> * nios2-rtems
> * or1k-rtems
> * powerpc-rtems
> * riscv-rtems
> * sh-rtems
> * sparc-rtems
> * sparc64-rtems
> * v850-rtems
> * x86_64-rtems
>
> Only powerpc-rtems and v850-rtems had these linker issues with -fno-common.
>
next prev parent reply other threads:[~2020-07-03 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 15:40 Joel Brobecker
2020-07-01 21:11 ` Rainer Orth
2020-07-01 21:21 ` Joel Brobecker
2020-07-02 21:49 ` Simon Marchi
2020-07-03 15:10 ` Joel Brobecker
2020-07-03 15:12 ` Simon Marchi
2020-07-10 23:07 ` Pedro Alves
2020-07-03 0:35 ` Simon Marchi
2020-07-03 7:30 ` Eli Zaretskii
2020-07-03 15:06 ` Joel Brobecker
2020-07-03 15:15 ` Simon Marchi
2020-07-03 8:15 ` Sebastian Huber
2020-07-03 13:07 ` Andrew Burgess [this message]
2020-07-03 15:07 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200703130708.GV2737@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox