public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghoort1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/68010] internal compiler error: in tree_to_shwi, at tree.h:3661
Date: Wed, 21 Oct 2015 20:15:00 -0000	[thread overview]
Message-ID: <bug-68010-4-KBTS6BAfUH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68010-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrey Chistyakov <ghoort1 at gmail dot com> ---
I simplified the Marcus' code:

Ghoort@blade /cygdrive/c/Projects/bug
$ cat c2.cpp
namespace boost {}

template <typename>
struct C {
};

template <typename Skipper> class StructDecoder : C<Skipper> {
public:
  StructDecoder()  {
    namespace bs = boost;
    using namespace bs;
  }
};

void NFGParserparse() {
  StructDecoder<int> q_syslog_desc;
}

Ghoort@blade /cygdrive/c/Projects/bug
$ g++ -c -g c2.cpp

c2.cpp: In constructor «StructDecoder<Skipper>::StructDecoder() [with Skipper =
int]»:
c2.cpp:12:3: internal compiler error: в tree_to_shwi, в tree.h:3661
   }
   ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
>From gcc-bugs-return-500213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 21 20:22:12 2015
Return-Path: <gcc-bugs-return-500213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8637 invoked by alias); 21 Oct 2015 20:22:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8592 invoked by uid 48); 21 Oct 2015 20:22:08 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/68043] New: many undocumented options, missing punctuation
Date: Wed, 21 Oct 2015 20:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-68043-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg01768.txt.bz2
Content-length: 1708

https://gcc.gnu.org/bugzilla/show_bug.cgi?idh043

            Bug ID: 68043
           Summary: many undocumented options, missing punctuation
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: msebor at gcc dot gnu.org
  Target Milestone: ---

As discussed in the thread at the link below, gcc's online help (the output of
gcc --help -v) includes a large number of undocumented options (197 in 5.1.0).
For  example, the section listing language-related options starts with the
following and 44 or so more undocumented options:

  The following options are language-related:
    --all-warnings           This switch lacks documentation
    --ansi                   This switch lacks documentation
    --assert                 This switch lacks documentation
    ...

All of the options in the section above and a good number of others are
synonyms for other options that are, in fact, documented.  This bug tracks an
enhancement to use this "aliasing" knowledge to avoid printing "This switch
lacks documentation" for such options and improve the experience using the
compiler.  In addition, as was also noted in the mailing list discussion, many
of the one-sentence descriptions of the options are not properly ended with a
period, making printing additional (generated) sentences difficult.  To make
that possible, the other aspect of this bug is to track fixing the sources of
the descriptions (i.e., the various .opt files) to properly terminate each
sentence.

https://gcc.gnu.org/ml/gcc-patches/2015-10/msg01395.html


  parent reply	other threads:[~2015-10-21 20:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 18:33 [Bug c++/68010] New: " ghoort1 at gmail dot com
2015-10-18 19:02 ` [Bug c++/68010] " ghoort1 at gmail dot com
2015-10-18 19:23 ` trippels at gcc dot gnu.org
2015-10-18 19:53 ` ghoort1 at gmail dot com
2015-10-18 20:18 ` [Bug debug/68010] " trippels at gcc dot gnu.org
2015-10-19 17:43 ` trippels at gcc dot gnu.org
2015-10-21 20:15 ` ghoort1 at gmail dot com [this message]
2015-10-22  7:48 ` trippels at gcc dot gnu.org
2021-08-13 21:46 ` [Bug debug/68010] ICE with -g and using namespace and namespace alias pinskia at gcc dot gnu.org
2024-03-25  5:25 ` [Bug debug/68010] [11/12/13/14 Regression] ICE with -g and using namespace and namespace alias inside a template class with dependent inheritance pinskia at gcc dot gnu.org

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-68010-4-KBTS6BAfUH@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).