public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug compile/18202] [compile] cv-qualified self-references crash
Date: Sat, 16 May 2015 12:43:00 -0000	[thread overview]
Message-ID: <bug-18202-4717-KfNzc94g4f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18202-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18202

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Kratochvil <jkratoch@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=3a9558c494e9b461f752ce26382701d4446f0958

commit 3a9558c494e9b461f752ce26382701d4446f0958
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Sat May 16 14:20:45 2015 +0200

    compile: Use -Wall, not -w

    For a reason unknown to me GDB was using -w instead of -Wall for 'compile
code'.
    The problem is later patch for 'compile printf' really needs some warnings
to
    be able to catch for example missing format string parameters:
        (gdb) compile printf "%d\n"
    GCC does not seem to be able to cancel -w (there is nothing like -no-w).

    Besides that I think even 'compile code' can benefit from -Wall.

    That #ifndef change in print_one_macro() is needed otherwise we get
    macro-redefinition warnings for the GCC built-in macros (as -w is no
    longer in effect).  For example, without the #ifndef/#endif one gets:

        compile -r -- void _gdb_expr(){int i = 5;}^M
        /tmp/gdbobj-xpU1yB/out4.c:4:0: warning: "__FILE__" redefined
[-Wbuiltin-macro-redefined]^M
        /tmp/gdbobj-xpU1yB/out4.c:5:0: warning: "__LINE__" redefined^M
        ...

    It makes more sense to pick the inferior's version of the macros, hence
    #ifndef instead of #undef.

    That new testsuite XFAIL is there as if one changes the struct definition
to be
    compliant with cv-qualifiers (to prevent the warnings):
    struct struct_type {
    -  struct struct_type *selffield;
    +  volatile struct struct_type *selffield;
    only then GCC/GDB will hit the crash, described in that GDB PR 18202.


    gdb/ChangeLog
    2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

        * compile/compile-c-support.c (print_one_macro): Use #ifndef.
        (generate_register_struct): Use __gdb_uintptr for TYPE_CODE_PTR.
        (c_compute_program): Call generate_register_struct after typedefs.
        * compile/compile-loc2c.c (push, pushf_register_address)
        (pushf_register): Cast to GCC_UINTPTR.
        (do_compile_dwarf_expr_to_c): Use unused attribute.  Add space after
        type.  Use GCC_UINTPTR instead of void *.  Remove excessive cast.
        (compile_dwarf_expr_to_c): Use GCC_UINTPTR instead of void *.
        * compile/compile.c (_initialize_compile): Enable warnings for
        COMPILE_ARGS.

    gdb/testsuite/ChangeLog
    2015-05-16  Jan Kratochvil  <jan.kratochvil@redhat.com>

        * gdb.compile/compile-ops.exp: Cast param to void.
        * gdb.compile/compile.exp: Complete type for _gdb_expr.
        (compile code struct_object.selffield = &struct_object): Add xfail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-05-16 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 13:59 [Bug compile/18202] New: " jan.kratochvil at redhat dot com
2015-04-10 12:18 ` [Bug compile/18202] " jan.kratochvil at redhat dot com
2015-05-16 12:43 ` cvs-commit at gcc dot gnu.org [this message]
2015-09-20 20:56 ` jan.kratochvil 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-18202-4717-KfNzc94g4f@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: 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).