unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Add tests with a local IFUNC resolver [BZ #23937]
Date: Mon, 4 Mar 2019 10:47:09 +0100 (CET)	[thread overview]
Message-ID: <56767244.124440.1551692830069@poczta.nazwa.pl> (raw)
In-Reply-To: <CAMe9rOoFBPwin0ZXVnv82Gu9Ft4=OYNyD4w6DCW_1G5M2v+Abg@mail.gmail.com>

2.03.2019 17:54 "H.J. Lu" <hjl.tools@gmail.com> wrote:
> 
> On Fri, Mar 1, 2019 at 4:34 PM Rafal Luzynski
> <digitalfreak@lingonborough.com> wrote:
> >
> > 1.03.2019 13:37 "H.J. Lu" <hjl.tools@gmail.com> wrote:
> > >
> > > On Fri, Mar 1, 2019 at 2:57 AM Rafal Luzynski
> > > <digitalfreak@lingonborough.com> wrote:
> > > >
> > > > 1.03.2019 09:41 Florian Weimer <fweimer@redhat.com> wrote:
> > > > > [...]
> > > > > What's your binutils version?
> > > >
> > > > 2.26.1
> > > >
> > >
> > > Try binutils 2.32.
> >
> > I've tried binutils-2.32-1.fc31.x86_64 from koji.fedoraproject.org
> > and it fails the same, just magic numbers slightly differ.
> >
> 
> GCC 6.4.1 and binutils 2.31 branch work for me on x86-64.

Still the same failure.

I've also checked a similar virtual machine on another physical
machine and again the same failure which confirms that it is not
anything specific to one CPU model.

Does it maybe matter that all my tests are performed in virtual
machines controlled by VirtualBox?

Regards,

Rafal

  reply	other threads:[~2019-03-04  9:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 12:53 [PATCH] elf: Add tests with a local IFUNC resolver [BZ #23937] Florian Weimer
2019-02-20 13:16 ` H.J. Lu
2019-02-20 13:29   ` Florian Weimer
2019-02-20 14:01     ` Szabolcs Nagy
2019-02-27 10:27 ` Florian Weimer
2019-03-01  0:50   ` Rafal Luzynski
2019-03-01  1:52     ` H.J. Lu
2019-03-01  8:25       ` Rafal Luzynski
2019-03-01  8:41         ` Florian Weimer
2019-03-01 11:03           ` Rafal Luzynski
2019-03-01 12:37             ` H.J. Lu
2019-03-02  0:34               ` Rafal Luzynski
2019-03-02 16:54                 ` H.J. Lu
2019-03-04  9:47                   ` Rafal Luzynski [this message]
2019-03-11 11:16                     ` Rafal Luzynski
2019-03-11 13:55                       ` Florian Weimer
2019-03-11 21:56                         ` Rafal Luzynski
2019-03-12  1:12                           ` H.J. Lu
2019-03-13 21:10                           ` Florian Weimer
2019-03-13 11:47                         ` Rafal Luzynski
2019-03-13 21:15                           ` Florian Weimer
2019-02-27 21:23 ` H.J. Lu

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56767244.124440.1551692830069@poczta.nazwa.pl \
    --to=digitalfreak@lingonborough.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@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).