public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@axis.com>
To: <law@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Deprecating cc0 (and consequently cc0 targets)
Date: Mon, 27 Jan 2020 14:35:00 -0000	[thread overview]
Message-ID: <202001271401.00RE1skf031563@ignucius.se.axis.com> (raw)
In-Reply-To: <1ee03bc0-ad1a-46dd-87bb-8288e990ce20@redhat.com> (message from	Jeff Law on Fri, 20 Sep 2019 17:38:38 +0200)

> From: Jeff Law <law@redhat.com>
> Date: Fri, 20 Sep 2019 17:38:38 +0200

Hi.  I'm not going to question

> The first step in that process is to drop support for cc0.

but could you please elaborate on...

> [cc0 support in gcc core]
> code is broken in various ways,

> particularly WRT exceptions.

...that last part?

If you mean asynchronous exceptions then perhaps in theory,
except there's no need to (and no state to) "unwind" to
in-between cc0 setter and user.  But I guess that goes for
"MODE_CC" targets too; exception information isn't that precise.

> This patch deprecates the affected targets.

(Not applied yet?  Before the gcc-10 branch?  Can you please
consider dropping cris* from that part when rebasing it, as per
contents on master and my pledge to merge axis/cris-decc0?)

> diff --git a/gcc/config.gcc b/gcc/config.gcc
> index 69d0a024d85..0c1637e8be1 100644
> --- a/gcc/config.gcc
> +++ b/gcc/config.gcc
> @@ -248,6 +248,12 @@ md_file=
>  # Obsolete configurations.
>  case ${target} in
>    tile*-*-*				\
> +  avr*-*-*				\
> +  h8300*-*-*				\
> +  cris*-*-*				\
> +  m68k*-*-*				\
> +  vax*-*-*				\
> +  cr16*-*-*				\
>   )
>      if test "x$enable_obsolete" != xyes; then
> 	 echo "*** Configuration ${target} is obsolete." >&2
> @@ -273,7 +279,6 @@ case ${target} in
>   | arm*-*-uclinux*			\
>   | i[34567]86-go32-*			\
>   | i[34567]86-*-go32*			\
> - | m68k-*-uclinuxoldabi*		\
>   | mips64orion*-*-rtems*		\
>   | pdp11-*-bsd				\
>   | powerpc*-*-linux*paired*		\
> @@ -294,7 +299,6 @@ case ${target} in
>   | *-*-solaris2.[0-9].*			\
>   | *-*-solaris2.10*			\
>   | *-*-sysv*				\
> - | vax-*-vms*				\
>   )
> 	  echo "*** Configuration ${target} not supported" 1>&2
> 	  exit 1

Beware, the two last hunks shouldn't be applied, else the patch
will actually make m68k-*-uclinuxoldabi* andvax-*-vms* available
(by --enable-obsolete).

That part would go in when actually removing the targets.

I may have lost track of the conversation that followed; maybe
the patch was itself obsoleted.

brgds, H-P

  parent reply	other threads:[~2020-01-27 14:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 15:38 Jeff Law
2019-09-20 17:22 ` Richard Biener
2019-09-20 17:45   ` Jeff Law
2019-09-21 20:48     ` Paul Koning
2019-09-21 21:04       ` Jeff Law
2019-09-21 23:48         ` Segher Boessenkool
2019-09-22 12:02           ` Richard Biener
2019-09-20 17:24 ` Joseph Myers
2019-09-22 10:45 ` coypu
2019-10-29 12:33 ` John Paul Adrian Glaubitz
2019-10-29 20:16   ` Jeff Law
2019-10-30  8:29     ` Richard Biener
2019-10-30  9:09       ` Richard Sandiford
2019-10-30 17:57         ` Gunther Nikl
2019-10-30 17:57           ` John Paul Adrian Glaubitz
2019-10-30 18:10             ` Jeff Law
2019-10-30 17:57           ` Jeff Law
2019-10-30 18:32       ` Jeff Law
2019-10-30 19:34         ` Paul Koning
2019-10-30  8:49     ` John Paul Adrian Glaubitz
2019-10-31 22:16     ` Segher Boessenkool
2020-01-27 14:35 ` Hans-Peter Nilsson [this message]
2020-01-27 18:23   ` Jeff Law

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=202001271401.00RE1skf031563@ignucius.se.axis.com \
    --to=hp@axis.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).