From: Oleg Endo <oleg.endo@t-online.de>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Joseph Myers <joseph@codesourcery.com>
Subject: Re: [SH][committed] Remove SH5 support in compiler
Date: Wed, 11 May 2016 12:37:00 -0000 [thread overview]
Message-ID: <1462970246.29542.8.camel@t-online.de> (raw)
In-Reply-To: <1980937.ETICYXGPpg@polaris>
On Wed, 2016-05-04 at 00:42 +0200, Eric Botcazou wrote:
> > Did that. Looks there are no changes after regeneration.
>
> Not in the libada directory:
>
> eric@polaris:~/svn/gcc/libada> svn info configure configure.ac
> Path: configure
> Name: configure
> Working Copy Root Path: /home/eric/svn/gcc
> URL: svn+ssh://gcc.gnu.org/svn/gcc/trunk/libada/configure
> Relative URL: ^/trunk/libada/configure
> Repository Root: svn+ssh://gcc.gnu.org/svn/gcc
> Repository UUID: 138bc75d-0d04-0410-961f-82ee72b054a4
> Revision: 235678
> Node Kind: file
> Schedule: normal
> Last Changed Author: olegendo
> Last Changed Rev: 235676
> Last Changed Date: 2016-04-30 11:11:03 +0200 (Sat, 30 Apr 2016)
> Text Last Updated: 2016-04-30 12:43:53 +0200 (Sat, 30 Apr 2016)
> Checksum: 81a247fa3a0b075a9d5912fc76108ca80958bf4d
>
> Path: configure.ac
> Name: configure.ac
> Working Copy Root Path: /home/eric/svn/gcc
> URL: svn+ssh://gcc.gnu.org/svn/gcc/trunk/libada/configure.ac
> Relative URL: ^/trunk/libada/configure.ac
> Repository Root: svn+ssh://gcc.gnu.org/svn/gcc
> Repository UUID: 138bc75d-0d04-0410-961f-82ee72b054a4
> Revision: 235678
> Node Kind: file
> Schedule: normal
> Last Changed Author: jakub
> Last Changed Rev: 232055
> Last Changed Date: 2016-01-04 15:30:50 +0100 (Mon, 04 Jan 2016)
> Text Last Updated: 2016-01-06 08:00:38 +0100 (Wed, 06 Jan 2016)
> Checksum: 33d89322bb3530f3c351968d9d127c6af002acf7
>
> You cannot change any configure files without changing configure.ac.
Ugh, sorry. Those pieces that I've changed manually are pulled from
the GNU config repo. At least that's what I understand. My proposed
changes to remove SH5 support in GNU config were rejected. I will
revert the corresponding changes in GCC.
Cheers,
Oleg
prev parent reply other threads:[~2016-05-11 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 1:27 Oleg Endo
2016-04-29 10:45 ` Oleg Endo
2016-04-29 14:11 ` Oleg Endo
2016-04-30 1:58 ` Oleg Endo
2016-04-30 5:44 ` Oleg Endo
2016-04-30 9:22 ` Oleg Endo
2016-04-30 9:39 ` Joseph Myers
2016-04-30 11:02 ` Oleg Endo
2016-05-03 22:42 ` Eric Botcazou
2016-05-11 12:37 ` Oleg Endo [this message]
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=1462970246.29542.8.camel@t-online.de \
--to=oleg.endo@t-online.de \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.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).