public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Shahab Vahedi <Shahab.Vahedi@synopsys.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>,
	Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>,
	Shahab Vahedi <Shahab.Vahedi@synopsys.com>
Subject: Re: [PATCH] Add support for ARCv2
Date: Wed, 9 Nov 2022 16:33:47 +0000	[thread overview]
Message-ID: <fb410039-8e20-ea1e-b7b2-7fba34740a91@synopsys.com> (raw)
In-Reply-To: <Y2GJNORKSebj4pk0@wildebeest.org>

Hi Mark,

On 11/1/22 22:01, Mark Wielaard wrote:
> On Mon, Oct 31, 2022 at 02:54:33PM +0000, Shahab Vahedi via Elfutils-devel wrote:
>> To be clear, these are the test results on a build without the patch AND
>> with the patch. I'm not sure why it happens even without the patch on
>> my system. If you want, I can file a bug report with more details.
> 
> Aha, sorry, I missed this was on x86_64. That is indeed odd. If you
> could file a bug report with your environment where this fails that
> would be good.

It has been filed [1].

[1]
https://sourceware.org/bugzilla/show_bug.cgi?id=29767

-- 
Shahab


  reply	other threads:[~2022-11-09 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28 13:43 Shahab Vahedi
2022-10-31 14:52 ` [PATCH v2] " Shahab Vahedi
     [not found] ` <Y13Tk6e/qsoolka+@wildebeest.org>
2022-10-31 14:54   ` [PATCH] " Shahab Vahedi
2022-11-01 21:01     ` Mark Wielaard
2022-11-09 16:33       ` Shahab Vahedi [this message]
2022-11-30  8:15       ` Shahab Vahedi
2022-11-30 23:36         ` Mark Wielaard
2022-12-01  9:44           ` Shahab Vahedi
2022-12-13 14:05             ` Mark Wielaard
2022-12-15  8:49               ` Shahab Vahedi

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=fb410039-8e20-ea1e-b7b2-7fba34740a91@synopsys.com \
    --to=shahab.vahedi@synopsys.com \
    --cc=Claudiu.Zissulescu@synopsys.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.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).