public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Mikhail Maltsev <maltsevm@gmail.com>,
	richard.sandiford@arm.com,
	       Trevor Saunders <"tbsaunde@tbsaunde.org"@redhat.com>
Cc: gcc-patches <gcc-patches@gnu.org>
Subject: Re: [PATCH, RFC]: Next stage1, refactoring: propagating rtx subclasses
Date: Tue, 12 May 2015 20:26:00 -0000	[thread overview]
Message-ID: <55525E1D.60900@redhat.com> (raw)
In-Reply-To: <555113DE.1080201@gmail.com>

On 05/11/2015 02:41 PM, Mikhail Maltsev wrote:
> On 09.05.2015 0:54, Jeff Law wrote:
>>
>> Both patches are approved.  Please install onto the trunk.
>>
>> jeff
>>
>
> Sorry for delay. When I started to work on this task, I wrote that I'll
> test the patches on couple of other platforms (not just x86). Probably I
> should have done it earlier, because I missed a couple of important
> details, which could break the build. Fortunately I did several tests
> before merging into trunk, and I think I need an advice on testing (or
> maybe some reworking).
It happens.  This kind of problem is part of what Trevor's patches are 
improving for us.

For many years, the preferred style of coding in GCC was to create 
target macros, the conditionalize code based on those macros.  That 
results in a lot of code in GCC that is rarely actually compiled.

>
> In general, is there a recommended set of targets that cover most
> conditionally compiled code? Also, the GCC Wiki mentions some automated
> test services and compile farm. Is it possible to use it to test a patch
> on many targets?
There's a makefile fragment in contrib which will build a large number 
of targets that you might find helpful.  Of course without some baseline 
to compare against, it's of less value.


>
> Finally, I could try to break the patch into smaller pieces, though I
> don't know if it's worth the efforts.
I doubt it's worth the effort at this point.


>
> P.S. Bootstrapped/regtested on x86_64-unknown-linux-gnu {,-m32}
> (C,C++,lto,objc,fortran,go), crosscompiled and regtested (C and C++
> testsuites) on sh-elf, mips-elf, poweperpc-eabisim and arm-eabi simulators.
These seem like a reasonable set of targets, especially if you could add 
one cc0 target (h8/300, v850, m68k come to mind as candidates).  I also 
doubt you need to do the full testing with simulators for this work. 
I'd think that bootstrapping one target, then just build the cross tools 
for the others would be fine.

jeff

  parent reply	other threads:[~2015-05-12 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31  4:38 Mikhail Maltsev
2015-03-31 15:52 ` Trevor Saunders
2015-04-02 21:13 ` Jeff Law
2015-04-25 11:49 ` Richard Sandiford
2015-04-27 16:38   ` Jeff Law
2015-04-27 16:57     ` Richard Sandiford
2015-04-27 20:01   ` Mikhail Maltsev
2015-04-28 13:50     ` Richard Sandiford
2015-04-28 17:12       ` Jeff Law
2015-04-29  8:02       ` Mikhail Maltsev
2015-04-30  3:54         ` Jeff Law
2015-04-30  5:46         ` Jeff Law
2015-05-04 20:32           ` Mikhail Maltsev
2015-05-04 21:22             ` Trevor Saunders
2015-05-09  5:49             ` Trevor Saunders
     [not found]           ` <5547D40F.6010802@gmail.com>
2015-05-08 21:54             ` Jeff Law
2015-05-11 20:41               ` Mikhail Maltsev
2015-05-11 21:21                 ` Joseph Myers
2015-05-12 20:26                 ` Jeff Law [this message]
2015-06-06  5:51               ` Mikhail Maltsev
2015-04-28 23:55     ` 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=55525E1D.60900@redhat.com \
    --to=law@redhat.com \
    --cc="tbsaunde@tbsaunde.org"@redhat.com \
    --cc=gcc-patches@gnu.org \
    --cc=maltsevm@gmail.com \
    --cc=richard.sandiford@arm.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).