From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2CC6D398EC11; Tue, 4 May 2021 14:56:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2CC6D398EC11 From: "nsz at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug libc/27824] New: preadv2 and pwritev2 offset argument passing on 64bit targets Date: Tue, 04 May 2021 14:56:05 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.33 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nsz at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot 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 cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2021 14:56:06 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D27824 Bug ID: 27824 Summary: preadv2 and pwritev2 offset argument passing on 64bit targets Product: glibc Version: 2.33 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: nsz at gcc dot gnu.org CC: drepper.fsp at gmail dot com Target Milestone: --- the linux preadv2 offset arg passing code is /* Provide a macro to pass the off{64}_t argument on p{readv,writev}{64}. = */ #define LO_HI_LONG(val) \ (long) (val), \ (long) (((uint64_t) (val)) >> 32) on a 64bit target the first arg contains the entire 64bit offset but i'd expect the second arg to be fixed 0. linux does not seem to look at the second arg now on 64bit targets, but it seems cleaner to pass 0 instead of top 32bit of val. x86_64 seems to fixed this but other targets still have the >> 32 logic. --=20 You are receiving this mail because: You are on the CC list for the bug.=