public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Rafael Ávila de Espíndola" <respindola@mozilla.com>
To: libffi-discuss@sourceware.org
Subject: Re: [patch] Check for libffi_cv_as_x86_pcrel should not look for just "warning"
Date: Sun, 27 Mar 2011 03:55:00 -0000	[thread overview]
Message-ID: <4D8EB535.2050804@mozilla.com> (raw)
In-Reply-To: <4D4C62FE.4070409@mozilla.com>

Ping.

FYI, this is https://bugzilla.mozilla.org/show_bug.cgi?id=631928

On 11-02-04 3:35 PM, Rafael Avila de Espindola wrote:
> The check that sets libffi_cv_as_x86_pcrel currently check for "warning"
> or "illegal". The problem is that when trying to build libffi with LTO
> clang will produce the warning
>
> clang: warning: argument unused during compilation: '-emit-llvm'
>
> The attached patch just uses the $CC error code instead. Is that OK or
> is there some strange assembler out there that rejects the assembly bug
> exists with 0?

Cheers,
Rafael

      reply	other threads:[~2011-03-27  3:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 20:36 Rafael Avila de Espindola
2011-03-27  3:55 ` Rafael Ávila de Espíndola [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=4D8EB535.2050804@mozilla.com \
    --to=respindola@mozilla.com \
    --cc=libffi-discuss@sourceware.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).