From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 685613858D37; Fri, 26 Jan 2024 03:50:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 685613858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1706241006;
	bh=kzA52s/c+z5nh5pf+PnCX4aLrzEYVQcJDOHKwF1yLF8=;
	h=From:To:Subject:Date:From;
	b=WjG0B8LnOtsZokbrZP8ak695JA89zhm9kVX020GFDAosyqrfLSrbUolBiqNZNnZRy
	 92wxkzesZnm8NczGFBkbtYppLN/Ar8e4wRE+ACYk4f9bCnwqUgieBnyXDKPQHVxXxB
	 EQajaSZlLm7YYRNNDmq66QIYZeTZ3UbWjXKQLqkk=
From: "mike at flyn dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/113610] New: Manpage could be more clear about gcc's -e flag
Date: Fri, 26 Jan 2024 03:50:05 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 13.2.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mike at flyn dot 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-113610-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

            Bug ID: 113610
           Summary: Manpage could be more clear about gcc's -e flag
           Product: gcc
           Version: 13.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mike at flyn dot org
  Target Milestone: ---

The GCC manpage states this:

-e entry
--entry=3Dentry
    Specify that the program entry point is entry. The argument is interpre=
ted
    by the linker; the GNU linker accepts either a symbol name or an addres=
s.

It might be worth noting that this refers to _start, and not main. Many
references refer to main as the "entry point" for a C program. Of course,
thinking this here fails to realize there is significant initialization that
will not happen when using -e. Either mentioning _start explicitly or noting
that changing the entry point might leave things like the heap uninitialize=
d (I
think) might help.

The same can be said about the ld manpage.=