public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Gaius Mulley <gaius.mulley@southwales.ac.uk>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Mon, 08 Jul 2019 15:31:00 -0000	[thread overview]
Message-ID: <yddimscr1ff.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87bly4d0qu.fsf@j228-gm.comp.glam.ac.uk> (Gaius Mulley's message	of "Mon, 08 Jul 2019 16:06:33 +0100")

Hi Gaius,

>> I meant to give a build with gm2 included a try on Solaris, but ended up
>> pretty much confused:
>>
>> * I've started with the gm2 repo on savannah.  Running the combine-trees
>>   script on master tried to combine gm2 with gcc 4.7.4.  Trying again
>>   with configure --with-gcc=none (no branch, for trunk?) didn't work
>>   either (don't remember the details off-hand).
>>
>> * Next, I discovered and tried the gcc_trunk branch there.  While it
>>   matches the patch set you sent here, it lacks most of the compiler
>>   proper, which only lives on master!?  In addition, the patches in
>>   there lack support for building libgm2.  Those are present on the
>>   master branch (which has both trunk and trunc in
>>   gcc-versionno/gcc/gm2/patches/gcc).  I tried to merge the trees and
>>   apply the patches manually, but failed again later.
>>
>> At this point, I gave up.  Am I missing something fundamental here?
>>
>> Thanks.
>>         Rainer
>
> Hi Rainer,
>
> it rather depends upon what you want, if you want the latest complete
> gm2 grafting onto the svn gcc trunk then these two scripts will create a
> patched tree and also rebuild gm2.

that's my goal: I'd like to see if gm2 and libgm2 build on Solaris and
pass at least a reasonable number of tests.

> [however please be careful with the scripts - they do assume that
> everything will be built in $HOME/GM2 - read and adapt as necessary].

Ok, I will give it a try.

> These will build a complete gm2 (from the master) - whereas the gcc_trunk
> branch is used to track the patches which are posted to gcc-patches
> (which are currently minimal and just build the gm2 driver).

That explains the difference.  While the driver are certainly important
for review, they don't help much by themselves when building the code...

> these tarballs are created using combine-trees, hope this helps,

Certainly.  Thanks a lot.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2019-07-08 15:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 13:10 Gaius Mulley
2019-06-29 10:15 ` Richard Sandiford
2019-06-29 12:52   ` Richard Biener
2019-06-29 20:29   ` Gaius Mulley
2019-06-29 18:08 ` Segher Boessenkool
2019-07-02  0:18   ` Gaius Mulley
2019-07-03  8:41 ` Rainer Orth
2019-07-08 15:20   ` Gaius Mulley
2019-07-08 15:31     ` Rainer Orth [this message]
2019-07-09  9:25       ` Rainer Orth
2019-07-09 11:41         ` Gaius Mulley
2019-07-10 11:50           ` Rainer Orth
2019-07-08 15:41     ` Gaius Mulley
2019-07-08 21:21 ` Matthias Klose
2019-07-09  6:37   ` Matthias Klose
2019-07-09 19:50     ` Gaius Mulley
2019-07-09 21:35       ` Matthias Klose
2019-07-10 17:56         ` Matthias Klose
2019-07-10 20:18           ` Gaius Mulley
2019-07-10 20:38             ` Matthias Klose
2019-07-10 21:16               ` Gaius Mulley
2019-07-09  9:56   ` Matthias Klose
2019-07-09 12:14     ` Gaius Mulley
2019-07-09 13:24       ` Matthias Klose
2019-07-09 13:49         ` Gaius Mulley
2019-07-09 16:23           ` Matthias Klose
2019-07-09 17:22             ` Gaius Mulley
2019-07-09 12:31   ` Rainer Orth
2019-07-09 15:57     ` Gaius Mulley
2019-07-09 17:32       ` Matthias Klose
2019-07-10 20:45         ` Gaius Mulley
2019-07-10 12:11       ` Rainer Orth
2019-07-09 21:36   ` Matthias Klose
2019-07-10 17:11     ` Matthias Klose
2019-07-10 20:49       ` Gaius Mulley
2019-07-11  7:57   ` Matthias Klose
2019-07-11 12:12     ` Gaius Mulley
2019-07-11 16:40       ` Segher Boessenkool
2019-07-11 17:26         ` Gaius Mulley
2019-07-12 15:41           ` Segher Boessenkool
2019-07-12 18:35             ` Gaius Mulley
2019-07-18 20:15   ` Matthias Klose
2019-11-20 10:10     ` Gaius Mulley
2019-07-19 14:22 ` Matthias Klose
2019-07-20 21:41 ` Matthias Klose

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=yddimscr1ff.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gaius.mulley@southwales.ac.uk \
    --cc=gcc-patches@gcc.gnu.org \
    /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).