This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 04/12] Add a generic significand implementation

From: Joseph Myers <joseph at codesourcery dot com>
To: Tulio Magno Quites Machado Filho <tuliom at linux dot ibm dot com>
Cc: <libc-alpha at sourceware dot org>
Date: Thu, 21 Jun 2018 17:00:23 +0000
Subject: Re: [PATCH 04/12] Add a generic significand implementation
References: <20180620020426.20372-1-tuliom@linux.ibm.com> <20180620020426.20372-5-tuliom@linux.ibm.com> <alpine.DEB.2.20.1806202034030.31467@digraph.polyomino.org.uk>

This patch has, as shown by build-many-glibcs.py, broken the build for 
m68k, because of how files there include files for other functions that 
operate as a form of generic implementation, and includes of 
<s_significand.c> seem to end up including the file generated from the 
template.  I'm guessing that rearranging things so that s_log1p.c rather 
than s_significand.c is the main implementation file used for that pair of 
functions should fix things.

-- 
Joseph S. Myers
joseph@codesourcery.com

Follow-Ups:
- [PATCH] m68k: Reorganize log1p and significand implementations
  - From: Tulio Magno Quites Machado Filho

References:
- [PATCHv2 00/12] Introduce ieee128 symbols and redirections
  - From: Tulio Magno Quites Machado Filho
- [PATCH 04/12] Add a generic significand implementation
  - From: Tulio Magno Quites Machado Filho
- Re: [PATCH 04/12] Add a generic significand implementation
  - From: Joseph Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]