buildroot.busybox.net archive mirror
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15006] New: toolchain Arm AArch64 toolchain 11.2-2022.02
Date: Wed, 21 Sep 2022 20:19:38 +0000	[thread overview]
Message-ID: <bug-15006-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15006

            Bug ID: 15006
           Summary: toolchain Arm AArch64 toolchain 11.2-2022.02
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: romain.naour@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Hello,

I'm using the current Buildroot master branch after the 2022.08 release and
after the merge of the next branch that include a ARM toolchain version bump to
11.2-2022.02.

This toolchain trigger some "Illegal instruction" error on some x86_64 host
like Intel(R) Xeon(R) CPU X5670.

gfortran is not able to pass the check in helper.mk:

<built-in>: internal compiler error: Illegal instruction
0x7f42c83efd5f ???
        ./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x7f42c83dad09 __libc_start_main
        ../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

Disabling gfortran allows to continue the build but it break with busybox build
with similar errors:

free(): invalid next size (fast)
editors/awk.c: In function ‘parse_expr’:
editors/awk.c:608:21: internal compiler error: Aborted
  608 | #define G (*(struct globals2 *)ptr_to_globals)
      |                     ^~~~~~~~
editors/awk.c:642:23: note: in expansion of macro ‘G’
  642 | #define t_info       (G.t_info      )
      |                       ^
editors/awk.c:1406:41: note: in expansion of macro ‘t_info’
 1406 |                 cn = vn->r.n = new_node(t_info);
      |                                         ^~~~~~

during GIMPLE pass: strlen
networking/tc.c: In function ‘cbq_print_opt.isra’:
networking/tc.c:234:12: internal compiler error: Illegal instruction
  234 | static int cbq_print_opt(struct rtattr *opt)
      |            ^~~~~~~~~~~~~

free(): invalid pointer
during GIMPLE pass: ssa
coreutils/sort.c: In function ‘bb_ascii_toupper’:
coreutils/sort.c:648:1: internal compiler error: Aborted
  648 | }
      | ^

0x7f107f6b2d5f ???
        ./signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x7f107f6b2ce1 __GI_raise
        ../sysdeps/unix/sysv/linux/raise.c:51
0x7f107f69c536 __GI_abort
        ./stdlib/abort.c:79
0x7f107f6f5767 __libc_message
        ../sysdeps/posix/libc_fatal.c:155
0x7f107f6fca59 malloc_printerr
        ./malloc/malloc.c:5347
0x7f107f6fdc13 _int_free
        ./malloc/malloc.c:4173
0x7f107f69dd09 __libc_start_main
        ../csu/libc-start.c:308
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://bugs.linaro.org/> for instructions.

It happen with the arm and aarch64 target.

Tested with Intel(R) Core(TM) i7-10850H cpu doesn't trigger such problem.

Best regards,
Romain

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-09-21 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 20:19 bugzilla [this message]
2022-09-21 21:16 ` [Buildroot] [Bug 15006] toolchain Arm AArch64 toolchain 11.2-2022.02 bugzilla
2022-10-25 20:13 ` bugzilla

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-15006-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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).