On Sun, 1 Apr 2018, Gerald Pfeifer wrote:
> And now to the most important question of all. ;-) Should we use
> "file name" or "filename" when referring to the name of a file?
See the GNU Coding Standards:
Please do not use the term ``pathname'' that is used in Unix
documentation; use ``file
On Tue, 20 Feb 2018, Bogdan Harjoc wrote:
> __VA_OPT__ was documented after 7.3.0 and the eprintf example for it
> ends with two backslashes instead of one:
>
> https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html
Thank you for reporting this, Bogdan.
I just fixed this per the patch below.
G
It turns out (all from krister, I am still totally lost) that it is not
failing for this specific reason in this case.
Rather, the attached patch from krister fixes it, saying that gcc
wants to change the label and then doesn't recognise the new insn
thinking the memory_operand predicate is not sa
On 03/28/2018 05:31 PM, Sirish Pande wrote:
Hi,
I am interested to know if there is any option that would tell me how many
registers have spilled. I noticed that there is spilled_regs array in
reload1.c - but I can't seem to find where it dumps that information.
Potentially I could build compi
On Sun, Apr 1, 2018 at 7:34 AM, Jason Vas Dias wrote:
> And even worse, the obvious workaround does not work:
>
> static inline __attribute__((always_inline))
> void foo(void) {}
>
> // static inline __attribute__((always_inline, alias("foo")))
> // void bar(void);
>
> static inline
Jason,
The manual mentions some C++-only options in the language
independent section 3.8 Options to Request or Suppress
Warnings and others in 3.5 Options Controlling C++ Dialect.
For example, -Wcatch-value, -Wconditionally-supported,
and -Wzero-as-null-pointer-constant are mentioned only
on the
