public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/105302] gccgo for Windows using MinGW-w64
Date: Tue, 19 Apr 2022 14:29:33 +0000	[thread overview]
Message-ID: <bug-105302-4-8BjU7ZJMhp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105302-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105302

--- Comment #5 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
The generated internal/cpu.gox looks like the below dump. Can you see what the
issue is with the magic string?
```
00000000: 6486 0100 0000 0000 5809 0000 0200 0000  d.......X.......
00000010: 0000 0500 2f34 0000 0000 0000 0000 0000  ..../4..........
00000020: 0000 0000 1c09 0000 3c00 0000 0000 0000  ........<.......
00000030: 0000 0000 0000 0000 4000 3040 7633 3b0a  ........@.0@v3;.
00000040: 7061 636b 6167 6520 6370 750a 706b 6770  package cpu.pkgp
00000050: 6174 6820 696e 7465 726e 616c 2f63 7075  ath internal/cpu
00000060: 0a69 6e69 7420 6370 7520 696e 7465 726e  .init cpu intern
00000070: 616c 5f31 6370 752e 2e69 6d70 6f72 740a  al_1cpu..import.
00000080: 7479 7065 7320 3134 2032 2033 3120 3130  types 14 2 31 10
00000090: 2032 3220 3435 2034 3031 2032 3539 2031   22 45 401 259 1
000000a0: 3531 2038 3920 3131 3220 3530 3320 3235  51 89 112 503 25
000000b0: 2032 3120 3232 0a74 7970 6520 3120 2243   21 22.type 1 "C
000000c0: 6163 6865 4c69 6e65 5061 6422 203c 7479  acheLinePad" <ty
000000d0: 7065 2034 3e0a 7479 7065 2032 2028 290a  pe 4>.type 2 ().
000000e0: 7479 7065 2033 2028 3f20 3c74 7970 6520  type 3 (? <type
000000f0: 2d31 363e 290a 7479 7065 2034 2073 7472  -16>).type 4 str
```

  parent reply	other threads:[~2022-04-19 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  7:59 [Bug go/105302] New: " brechtsanders at users dot sourceforge.net
2022-04-18  8:29 ` [Bug go/105302] " brechtsanders at users dot sourceforge.net
2022-04-18 19:43 ` ian at airs dot com
2022-04-18 19:58 ` brechtsanders at users dot sourceforge.net
2022-04-18 20:01 ` ian at airs dot com
2022-04-19 14:29 ` brechtsanders at users dot sourceforge.net [this message]
2022-04-19 16:08 ` ian at airs dot com
2022-04-19 21:21 ` brechtsanders at users dot sourceforge.net
2022-04-19 22:36 ` ian at airs dot com

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=bug-105302-4-8BjU7ZJMhp@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).