本批发*商*行专销由烟草漏税香烟！2019/4/16
中华（软329）￥380 （硬盒）￥280 :
芙蓉王（硬）￥160 黄鹤楼（1916）￥400
品种多多不一一介绍需要V信咨询；
李*经*理；134-1693-7477 V信同号 11:27
2019/4/16
The following code will emit a warning with -Wattributes:
[[some_ns::some_attribute]]
void call_me();
:2:14: warning: 'some_ns::some_attribute' scoped attribute
directive ignored [-Wattributes]
2 | void call_me();
| ^
I want to disable the warning for third party attribute
\0Ae6Cv84�7AN30�1F�D0[A2b37�1A `A8Y7D gcc@gcc.gnu.org
a1F�22`A8�09bE9�7AN30�1F�D0N3A`A8cD0O9Bv84e36m3Eg0DRA1002
`A8u33�F7v84u35[50SD1y68]F2b10R9F_00Q77�01SD1y68�E6`C5Y82N0B�1A
SD1y68NE3x01�1A019093877133873SD1y68SF7x01�1A5123338323SD1y68�D1�9D�1A6539.9Q43
S05T2Bv84�D0S55SF7�1A `A8SEFNE5p
Am 15.04.2019 um 17:43 schrieb Rainer Emrich:
> Am 15.04.2019 um 17:38 schrieb Jakub Jelinek:
>> On Mon, Apr 15, 2019 at 05:30:14PM +0200, Rainer Emrich wrote:
>>> There seems to be a generic issue with the tests in gcc/testsuite. The
>>> log files do not contain the logs.
>>
>> Perhaps contrib/dg-
Am 15.04.2019 um 17:38 schrieb Jakub Jelinek:
> On Mon, Apr 15, 2019 at 05:30:14PM +0200, Rainer Emrich wrote:
>> There seems to be a generic issue with the tests in gcc/testsuite. The
>> log files do not contain the logs.
>
> Perhaps contrib/dg-extract-results* misbehaved?
> Can you look for the
On Mon, Apr 15, 2019 at 05:30:14PM +0200, Rainer Emrich wrote:
> There seems to be a generic issue with the tests in gcc/testsuite. The
> log files do not contain the logs.
Perhaps contrib/dg-extract-results* misbehaved?
Can you look for the testsuite/g++*/g++.log.sep files? Do they contain
every
Am 15.04.2019 um 17:22 schrieb Rainer Emrich:
> Today I had the chance to bootstrap and runthe testsuite for trunk on
> x86_64-w64-mingw32. Bootstrap is done with all supported languages
> enabled including "D".
>
> Testsuite results can be found here:
> https://gcc.gnu.org/ml/gcc-testresults/2019
Today I had the chance to bootstrap and runthe testsuite for trunk on
x86_64-w64-mingw32. Bootstrap is done with all supported languages
enabled including "D".
Testsuite results can be found here:
https://gcc.gnu.org/ml/gcc-testresults/2019-04/msg01795.html
Complete logs here:
https://cloud.emric
Hi,
On Mon, 15 Apr 2019, Jakub Jelinek wrote:
> > It seems the C++ parser got quite a bit slower with gcc 9 :-( Most
> > visible in the compile time for tramp-3d (24%) and kdecore.cc (18%
> > slower with just PGO); it seems that the other .ii files are C-like
> > enough to not
>
> Is that wit
On Mon, Apr 15, 2019 at 12:12:13PM +, Michael Matz wrote:
> Hi,
>
> On Mon, 15 Apr 2019, Martin Liška wrote:
>
> > There's a similar comparison that I did for the official openSUSE gcc
> > packages. gcc8 is built with PGO, while the gcc9 package is built in 2
> > different configurations: P
> Hi,
>
> On Mon, 15 Apr 2019, Martin Liška wrote:
>
> > There's a similar comparison that I did for the official openSUSE gcc
> > packages. gcc8 is built with PGO, while the gcc9 package is built in 2
> > different configurations: PGO, LTO, PGO+LTO (LTO used for FE in stage4,
> > for generato
Hi,
On Mon, 15 Apr 2019, Martin Liška wrote:
> There's a similar comparison that I did for the official openSUSE gcc
> packages. gcc8 is built with PGO, while the gcc9 package is built in 2
> different configurations: PGO, LTO, PGO+LTO (LTO used for FE in stage4,
> for generators in stage3 as
Hi.
There's a similar comparison that I did for the official openSUSE gcc packages.
gcc8 is built with PGO, while the gcc9 package is built in 2 different
configurations:
PGO, LTO, PGO+LTO (LTO used for FE in stage4, for generators in stage3 as well).
Please take a look at attached statistics.
13 matches
Mail list logo
