On 11/28/18 5:05 PM, Martin Sebor wrote:
> On 11/27/18 10:47 AM, Joseph Myers wrote:
>> On Mon, 26 Nov 2018, Martin Sebor wrote:
>>
>>> Ping: https://gcc.gnu.org/ml/gcc-patches/2018-11/msg01674.html
>>
>> This patch needs an update to the comment on convert_argument to explain
>> the semantics of t
On 11/27/18 10:47 AM, Joseph Myers wrote:
On Mon, 26 Nov 2018, Martin Sebor wrote:
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-11/msg01674.html
This patch needs an update to the comment on convert_argument to explain
the semantics of the new valtype parameter and how it differs from the
pre
On Mon, 26 Nov 2018, Martin Sebor wrote:
> Ping: https://gcc.gnu.org/ml/gcc-patches/2018-11/msg01674.html
This patch needs an update to the comment on convert_argument to explain
the semantics of the new valtype parameter and how it differs from the
previously used TREE_TYPE (val).
--
Joseph
Ping: https://gcc.gnu.org/ml/gcc-patches/2018-11/msg01674.html
On 11/19/18 6:14 PM, Martin Sebor wrote:
The recent -Wbuiltin-declaration-mismatch enhancement to detect
calls with incompatible arguments to built-ins declared without
a prototype introduced a subtle bug in the detection of floating
The recent -Wbuiltin-declaration-mismatch enhancement to detect
calls with incompatible arguments to built-ins declared without
a prototype introduced a subtle bug in the detection of floating
conversion errors when passing EXCESS_PRECISION_EXPR arguments
to floating function parameters with diffe
