public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: binutils@sourceware.org, fche@sourceware.org
Subject: Re: [RFA] fix mingw32  --enable-targets=all --enable-64-bit-bfd failure in or1k-desc.h
Date: Mon, 19 May 2014 00:46:00 -0000	[thread overview]
Message-ID: <20140519004639.GK5162@bubble.grove.modra.org> (raw)
In-Reply-To: <5377d006.617a420a.5cb0.ffffeacbSMTPIN_ADDED_BROKEN@mx.google.com>

On Sat, May 17, 2014 at 11:09:06PM +0200, Pierre Muller wrote:
> 2014-05-17  Pierre Muller  <muller@sourceware.org>
> 
> 	* or1k-desc.h (enum spr_field_masks): Remove compilation warning
> 	on 32-bit systems.
> 
> diff --git a/opcodes/or1k-desc.h b/opcodes/or1k-desc.h

No, sorry, this file is generated.  If this patch is committed, it
will be undone next time the file is regenerated.  I suspect you'll
need to poke at cgen itself to fix this problem.

Which reminds me.  Frank, is there any chance of
https://sourceware.org/ml/cgen/2014-q2/msg00001.html
being committed so I can turn back on --enable-cgen-maint for binutils
builds?

-- 
Alan Modra
Australia Development Lab, IBM

       reply	other threads:[~2014-05-19  0:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5377d006.617a420a.5cb0.ffffeacbSMTPIN_ADDED_BROKEN@mx.google.com>
2014-05-19  0:46 ` Alan Modra [this message]
2014-05-19  0:54   ` Frank Ch. Eigler
2014-05-20  8:50   ` Pierre Muller
     [not found]   ` <537b174b.a413c20a.4a37.3c76SMTPIN_ADDED_BROKEN@mx.google.com>
2014-05-20 10:37     ` Alan Modra
2014-05-22  3:30       ` Stefan Kristiansson
2014-05-22  4:17         ` Alan Modra
2014-05-17 21:09 Pierre Muller

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=20140519004639.GK5162@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=fche@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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).