From owner-freebsd-toolchain@freebsd.org  Sun Nov 19 23:47:49 2017
Return-Path: <owner-freebsd-toolchain@freebsd.org>
Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCF56DC1279
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Sun, 19 Nov 2017 23:47:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CAFD168184
 for <freebsd-toolchain@FreeBSD.org>; Sun, 19 Nov 2017 23:47:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAJNlmiO075709
 for <freebsd-toolchain@FreeBSD.org>; Sun, 19 Nov 2017 23:47:49 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 223752] clang __attribute__((constructor)) gets wrong input
 parameters
Date: Sun, 19 Nov 2017 23:47:48 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: markmi@dsl-only.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-223752-29464-tq7jXx04Zo@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223752-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-223752-29464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Nov 2017 23:47:50 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223752

--- Comment #6 from Mark Millard <markmi@dsl-only.net> ---
(In reply to dstaesse from comment #4)

Also: in looking around I find that every
official webpage/document about this that
shows examples shows functions with no
arguments. (But none that I found has any
explicit words about the argument list
requirements. None say that the arguments
are the same as for any standard variation
for how main can be declared.)

For a stack architecture, there would be stack
pushes set up before the calls and pops set
up after the calls. In architectures with
some degree of register-based argument passing
it is harder to see what has a
garbage-in/garbage-out/accidental status vs.
what is deliberate.

It looks to me like the existing documentation
could stand an update about parameters and
arguments.

--=20
You are receiving this mail because:
You are the assignee for the bug.=