public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug server/15081] New: AX with gcc-4.8: Expression pieces exceed word size Date: Tue, 29 Jan 2013 17:47:00 -0000 [thread overview] Message-ID: <bug-15081-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15081 Bug #: 15081 Summary: AX with gcc-4.8: Expression pieces exceed word size Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: server AssignedTo: unassigned@sourceware.org ReportedBy: jan.kratochvil@redhat.com Classification: Unclassified Host: x86_64-unknown-linux-gnu Target: x86_64-unknown-linux-gnu Then there is in gdbserver mode: -PASS: gdb.trace/collection.exp: collect register locals collectively: start trace experiment +FAIL: gdb.trace/collection.exp: collect register locals collectively: start trace experiment due to: register int locar[4]; locar[0] = 121; locar[1] = 122; locar[2] = 123; locar[3] = 124; producing with gcc-4.8.0pre: DW_AT_location: (DW_OP_reg12(r12);DW_OP_piece:8;DW_OP_reg13(r13);DW_OP_piece:8) which cannot be handled by current AX: if (bits_collected + size > 8 * sizeof (LONGEST)) error (_("Expression pieces exceed word size")); as it is 128-bit variable (from two 64-bit registers). -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-01-29 17:47 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-29 17:47 jan.kratochvil at redhat dot com [this message] 2013-01-30 16:00 ` [Bug server/15081] " tromey at redhat 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-15081-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).