From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: Re: [TUHS] OT: compiler back-end bug
Date: Sun, 29 Sep 2019 10:47:26 +0100 [thread overview]
Message-ID: <20190929094726.6488620154@orac.inputplus.co.uk> (raw)
In-Reply-To: <20190929092158.GA27566@minnie.tuhs.org>
Hi Warren,
> If any of you have Intel ia64 skills and/or fixing compiler back-end
> bugs, could you contact me off-list?
Sorry, on list, but it may help the willing eyeballs if
> To see the original compiler's assembly version of fwrite():
>
> $ ./scc0 -S lib/fwrite.c
>
> To see my compiler's [faulty] assembly version of fwrite():
>
> $ ./myscc -S lib/fwrite.c
these two were made easily available, e.g. a pastebin like
curl -sSF 'f:1=<-' ix.io <lib/fwrite.c
as then spotting the cause of
> At present, my compiler fwrite() code is passing bogus arguments to
> memcpy() where it crashes with a segfault.
wouldn't involve downloads, make, etc., that make it easy to think one
doesn't have the time to look. :-)
--
Cheers, Ralph.
next prev parent reply other threads:[~2019-09-29 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 9:21 Warren Toomey
2019-09-29 9:47 ` Ralph Corderoy [this message]
2019-09-29 10:03 ` Warren Toomey
2019-09-29 10:50 ` Ralph Corderoy
2019-10-03 20:03 ` Steve Johnson
2019-10-03 20:03 ` Nemo Nusquam
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=20190929094726.6488620154@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).