From: "Frank Ch. Eigler" <fche@redhat.com>
To: Sergey Belyashov <sergey.belyashov@gmail.com>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
"Frank Ch. Eigler via Cgen" <cgen@sourceware.org>
Subject: Re: BUG: non-fixed-length ISAs are unsupported for now
Date: Thu, 13 Aug 2020 10:32:24 -0400 [thread overview]
Message-ID: <20200813143224.GC28536@redhat.com> (raw)
In-Reply-To: <CAOe0RDy0rdTxQjw-6xwE6gj3SeDf8biyonuOW-6OQTJwz1zE5w@mail.gmail.com>
Hi -
> When I increase base-insn-bitsize to 32 of ISA definition objdump
> fails with: stack smashing error. Valgrind shows next backtrace:
> [...]
> ==325050== by 0x17BE43: default_print_insn (z80-dis.c:448)
> ==325050== by 0x17C0AA: print_insn_z80 (z80-dis.c:567)
> ==325050== by 0x131CB3: disassemble_bytes (objdump.c:2768)
> ==325050== by 0x13360E: disassemble_section (objdump.c:3340)
OK, so things went much further. I'd work backward from this new
error rather than change the base-insn-size back. Can you push to
your branch all the cgen-generated opcodes/etc. code?
- FChE
next prev parent reply other threads:[~2020-08-13 14:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 13:37 Sergey Belyashov
2020-04-27 16:29 ` Frank Ch. Eigler
2020-04-27 17:00 ` Sergey Belyashov
2020-04-27 17:52 ` Sergey Belyashov
2020-04-27 18:03 ` Jose E. Marchesi
2020-04-27 19:34 ` Sergey Belyashov
2020-04-27 20:01 ` Jose E. Marchesi
2020-04-27 20:23 ` Sergey Belyashov
2020-04-29 19:11 ` Sergey Belyashov
2020-07-30 9:11 ` Sergey Belyashov
2020-08-11 15:38 ` Frank Ch. Eigler
2020-08-11 15:57 ` Sergey Belyashov
2020-08-11 16:08 ` Frank Ch. Eigler
2020-08-12 13:59 ` Sergey Belyashov
2020-08-12 18:36 ` Frank Ch. Eigler
2020-08-12 18:53 ` Jose E. Marchesi
2020-08-12 19:19 ` Sergey Belyashov
2020-08-12 19:21 ` Frank Ch. Eigler
2020-08-12 19:27 ` Jose E. Marchesi
2020-08-12 19:44 ` Sergey Belyashov
2020-08-12 19:57 ` Frank Ch. Eigler
2020-08-13 13:34 ` Sergey Belyashov
2020-08-13 14:32 ` Frank Ch. Eigler [this message]
2020-08-13 14:47 ` Sergey Belyashov
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=20200813143224.GC28536@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=sergey.belyashov@gmail.com \
/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).