Ok I'll do it.. Thanks!
On Thu, Sep 18, 2014 at 12:59 PM, Joel Sherrill
wrote:
>
> On 9/18/2014 10:40 AM, Marcos Díaz wrote:
>> What I printed is the internal representation of those types (at AST
>> of gcc), as I could see the types for each architecture are defined
>> with the macro WCHAR_TYPE
On 9/18/2014 10:00 AM, Marcos Díaz wrote:
> The output of the two types (debugging gcc at the comparison of types):
> For ARM (doesn't throw the warning):
>
> (gdb) p debug_tree(wanted_type)
>
> (gdb) p debug_tree(cur_type)
>
> For sparc: (throws the warning)
> p debug_tree(wanted_type)
>
>
The output of the two types (debugging gcc at the comparison of types):
For ARM (doesn't throw the warning):
(gdb) p debug_tree(wanted_type)
wrote:
> Hi, I've been looking this, and I saw the following:
> This warning arise because the %lc format option is for wint_t type,
> and we are passing a
Hi, I've been looking this, and I saw the following:
This warning arise because the %lc format option is for wint_t type,
and we are passing a wchar_t type.
At the architectures that doesn't give the warning, those two types
are the same (wint_t and wchar_t), and those who give the warning have
the
Thanks, I will look into it.
On Wed, Sep 17, 2014 at 4:02 PM, Joel Sherrill
wrote:
>
> On 9/17/2014 1:38 PM, Marcos Díaz wrote:
>> Where can we see in which BSP's and with which tools this warning was
>> generated? Thanks
> OK. It is with the tools generated by the current RSB and
> the RTEMS he
On 9/17/2014 1:38 PM, Marcos Díaz wrote:
> Where can we see in which BSP's and with which tools this warning was
> generated? Thanks
OK. It is with the tools generated by the current RSB and
the RTEMS head.
I have attached a cut down and script that I used to test it
on all RTEMS gcc's I have i
Where can we see in which BSP's and with which tools this warning was
generated? Thanks
On Wed, Sep 17, 2014 at 12:40 PM, Joel Sherrill
wrote:
>
> On 9/17/2014 10:23 AM, Daniel Gutson wrote:
>> Marcos and I will take a look.
> Thanks.
>>
>> On Wed, Sep 17, 2014 at 12:19 PM, Joel Sherrill
>> wrot
On 9/17/2014 10:23 AM, Daniel Gutson wrote:
> Marcos and I will take a look.
Thanks.
>
> On Wed, Sep 17, 2014 at 12:19 PM, Joel Sherrill
> wrote:
>> Hi
>>
>> I would really appreciate it if someone could look into this
>> warning and see if we can get an explanation. It could be
>> a source code
Marcos and I will take a look.
On Wed, Sep 17, 2014 at 12:19 PM, Joel Sherrill
wrote:
> Hi
>
> I would really appreciate it if someone could look into this
> warning and see if we can get an explanation. It could be
> a source code issue or something higher in the tools.
> It is reported on 120 B
Hi
I would really appreciate it if someone could look into this
warning and see if we can get an explanation. It could be
a source code issue or something higher in the tools.
It is reported on 120 BSP build configurations:
../../../../../../rtems/c/src/../../cpukit/libmisc/shell/hexdump-conv.c:1
10 matches
Mail list logo
