public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Edwards <mutazilah@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Re: gcc 3.2.3 x64 negative indexes
Date: Sun, 11 Feb 2024 03:48:42 +0800	[thread overview]
Message-ID: <CAMi4Nxbnq5=NxMZt1eH3pn8oJgNsWdCS75StqwmvjC9NEROxeQ@mail.gmail.com> (raw)
In-Reply-To: <CAMi4NxZvwKg_LLczPcrGt2Mv0J6_NVFqYd-96=hEZsWqHB5Qow@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

(replying to Joe Monk)

> It appears that this is not an issue that this version of GCC is
> architected to be able to solve.

> The first 64-bit PC processor, the AMD opteron series, was launched on
> April 22, 2003.

> GCC 3.2.3 was released on April 25, 2003.

Jakub has already shown correct x64 code being generated
by gcc 3.2.3. Maybe they used an emulator or something.

And I already have it running myself - with small modifications
for MSABI - on Windows 10 64-bit - for my pdptest test program.

The only thing not working for me at the moment that I know
about is negative indexes. And that is something specific to my
derivative (or more likely the way I built it), not standard gcc 3.2.3.

BFN. Paul.

  parent reply	other threads:[~2024-02-10 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 15:02 Paul Edwards
2024-02-07 15:12 ` Jakub Jelinek
2024-02-09 21:34   ` Paul Edwards
2024-02-09 21:38     ` Paul Edwards
2024-02-10 13:41       ` Paul Edwards
2024-02-10 17:42         ` Joe Monk
2024-02-10 19:48         ` Paul Edwards [this message]
2024-02-11  0:03         ` Paul Edwards

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='CAMi4Nxbnq5=NxMZt1eH3pn8oJgNsWdCS75StqwmvjC9NEROxeQ@mail.gmail.com' \
    --to=mutazilah@gmail.com \
    --cc=gcc@gcc.gnu.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).