- Package:
- gcc
- Source:
- gcc-defaults
- Description:
- GNU C compiler
- Submitter:
- Date:
- 2025-06-04 04:49:02 UTC
- Severity:
- wishlist
- Tags:
For the file
unsigned long foo(unsigned long a, unsigned long b) {
unsigned long c = a - b;
if (a < b) {
c += 100;
}
return c;
}
gcc -O2 -S generates
.file "subcmp.c"
.version "01.01"
gcc2_compiled.:
.text
.align 4
.globl foo
.type foo,@function
foo:
pushl %ebp
movl %esp,%ebp
movl 8(%ebp),%ecx
movl 12(%ebp),%eax
movl %ecx,%edx
subl %eax,%edx
cmpl %eax,%ecx
jae .L3
addl $100,%edx
.L3:
movl %edx,%eax
leave
ret
.Lfe1:
.size foo,.Lfe1-foo
.ident "GCC: (GNU) 2.95.2 20000220 (Debian GNU/Linux)"
The cmpl after the subl is unnecessary.
gcc-ss 2.97-0.1 generates pretty much the same code.
Thank you very much for your problem report. It has the internal identification `optimization/3507'. The individual assigned to look at your report is: unassigned.
# submitted Debian report #75773 to gcc-gnats as PR 3507 # http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3507&database=gcc forwarded 75773 gcc-gnats@gcc.gnu.org retitle 75773 [PR optimization/3507]: appalling optimisation with sub/cmp on i386 thanks
State-Changed-From-To: open->analyzed
State-Changed-By: rth
State-Changed-When: Tue Apr 2 02:36:06 2002
State-Changed-Why:
(set (reg/v:SI 61)
(minus:SI (reg/v:SI 59) (reg/v:SI 60)))
and
(set (reg:CC 17 flags)
(compare:CC (reg/v:SI 59) (reg/v:SI 60)))
are not LOG_LINK related, because they share no common
destination, so combine doesn't merge them. But after
reload, they don't have the same arguments, so we can't
peephole them there either.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3507
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Wed Apr 3 03:22:54 2002
State-Changed-Why:
This is tedious - can you stop Debbugs replying to GNATS?
They get themselves in a mail loop.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6132
State-Changed-From-To: open->closed
State-Changed-By: bangerth
State-Changed-When: Wed Dec 18 07:52:08 2002
State-Changed-Why:
Mail picked up accidentially.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6152
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507 pinskia at physics dot uc dot edu changed: What |Removed |Added ---------------------------------------------------------------------------- GCC target triplet|i386-linux |i386-linux, powerpc-*-* Last reconfirmed|0000-00-00 00:00:00 |2003-08-03 17:59:19 date| |------- Additional Comments From pinskia at physics dot uc dot edu 2003-08-03 17:59 ------- It also happens on powerpc-apple-darwin6.6 Currently GCC produces: _foo: cmplw cr0,r3,r4 subf r3,r4,r3 bgelr- cr0 addi r3,r3,100 blr But GCC should be able to produce: _foo: subf. r3,r4,r3 bgelr- cr0 addi r3,r3,100 blr Which is smaller (and faster on every thing except maybe 970 and Power4).------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Additional Comments From kazu at cs dot umass dot edu 2004-01-04 08:26 ------- Replacing a < b with (long) c < 0 sounds like a CSE type of work but does not quite fit in the current framework of replacing expensive expressions with cheaper equivalents that are already available. That is, nobody has computed (long) c < 0 before, so it's not available.------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
------- Additional Comments From cyrille at chepelov dot org 2004-03-03 19:46 ------- Observed on m68k-palmos (2.95.3+Debian boatload of patches), arm-palmos (3.2.2), AVR (3.3, 20030512 prerelease, likely patched), and on i386 (3.3.3, mainline and tree-ssa as of 20040302). I suggest updating $SUMMARY and $TARGET accordingly. Further testing (see attachement) show that opportunities can be missed even for simple signed ints: bar() has the problem, while baz() and bat() use either cmp or sub, but not both. Furthermore, baz() seems to show that the combine pass is doing a good job of finding the right compare instruction when the primary result of the subtraction is thrown away. Could it be possible that a simple and systematic: (a < b) ===> (coerce_to_signed_type<>(a - b) < 0) replacement (done perhaps at the SSA level) would resolve this, without incurring excessive costs?------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
------- Additional Comments From cyrille at chepelov dot org 2004-03-03 19:52 ------- Created an attachment (id=5856) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=5856&action=view) a variant test (with signed ints instead of unsigned longs -- same problem) bar() shows the same problem as the original poster baz() shows a variant of bar(), which although not semantically identical, shows on i386 that the RTL optimizer is able to use a cmp instruction anyway (also on AVR, but NOT on ARM). bat() is semantically identical to bar() (modulo possible data overflow), and shows the kind of code which would be expected from compiling bar().------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian at wasabisystems dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Additional Comments From steven at gcc dot gnu dot org 2005-01-23 14:57 ------- Still there as of 2005-01-23------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
--
What |Removed |Added
----------------------------------------------------------------------------
CC|rth at gcc dot gnu dot org |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2005-09-07 17:29:51 |2005-12-07 03:44:54
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2005-12-07 03:44:54 |2006-03-05 03:13:08
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Comment #7 from eweddington at cso dot atmel dot com 2007-08-23 20:10 -------
Confirmed for AVR. GCC 4.2.1 for avr generates this:
foo:
/* prologue: frame size=0 */
push r14
push r15
push r16
push r17
/* prologue end (size=4) */
movw r14,r22
movw r16,r24
sub r14,r18
sbc r15,r19
sbc r16,r20
sbc r17,r21
cp r22,r18
cpc r23,r19
cpc r24,r20
cpc r25,r21
brsh .L2
ldi r24,lo8(100)
ldi r25,hi8(100)
ldi r26,hlo8(100)
ldi r27,hhi8(100)
add r14,r24
adc r15,r25
adc r16,r26
adc r17,r27
.L2:
movw r24,r16
movw r22,r14
/* epilogue: frame size=0 */
pop r17
pop r16
pop r15
pop r14
ret
Ideally it should be something like:
foo:
/* prologue: frame size=0 */
sub r22,r18
sbc r23,r19
sbc r24,r20
sbc r25,r21
brcc .L2
ldi r18,lo8(100)
ldi r19,hi8(100)
ldi r20,hlo8(100)
ldi r21,hhi8(100)
add r22,r18
adc r23,r19
adc r24,r20
adc r25,r21
.L2:
/* epilogue: frame size=0 */
ret
Which is less than half the number of instructions.
Changing summary and target fields
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--
eweddington at cso dot atmel dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eweddington at cso dot atmel
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--
rask at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |rask at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
Last reconfirmed|2007-08-23 20:10:25 |2007-11-02 14:17:51
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Comment #8 from rask at gcc dot gnu dot org 2007-11-27 18:04 -------
Created an attachment (id=14647)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14647&action=view)
Patch to enhance cse.c
The attached patch can optimize this testcase:
void foo (int);
int bar2 (int a, int b)
{
int c = a - b;
if (a < b)
{
foo (c);
}
return c;
}
Before:
bar2:
pushl %ebx # 33 *pushsi2 [length = 1]
subl $8, %esp # 34 pro_epilogue_adjust_stack_1/1 [length
= 3]
movl 16(%esp), %edx # 2 *movsi_1/1 [length = 4]
movl 20(%esp), %eax # 3 *movsi_1/1 [length = 4]
movl %edx, %ebx # 32 *movsi_1/1 [length = 2]
subl %eax, %ebx # 7 *subsi_1/1 [length = 2]
cmpl %eax, %edx # 8 *cmpsi_1_insn/1 [length = 2]
jge .L2 # 9 *jcc_1 [length = 2]
movl %ebx, (%esp) # 11 *movsi_1/2 [length = 3]
call foo # 12 *call_0 [length = 5]
.L2:
movl %ebx, %eax # 19 *movsi_1/1 [length = 2]
addl $8, %esp # 37 pro_epilogue_adjust_stack_1/1 [length
= 3]
popl %ebx # 38 popsi1 [length = 1]
ret # 39 return_internal [length = 1]
After:
bar2:
pushl %ebx # 33 *pushsi2 [length = 1]
subl $8, %esp # 34 pro_epilogue_adjust_stack_1/1 [length
= 3]
movl 16(%esp), %eax # 2 *movsi_1/1 [length = 4]
movl %eax, %ebx # 32 *movsi_1/1 [length = 2]
subl 20(%esp), %ebx # 8 *subsi_2/2 [length = 4]
jns .L2 # 9 *jcc_1 [length = 2]
movl %ebx, (%esp) # 11 *movsi_1/2 [length = 3]
call foo # 12 *call_0 [length = 5]
.L2:
movl %ebx, %eax # 19 *movsi_1/1 [length = 2]
addl $8, %esp # 37 pro_epilogue_adjust_stack_1/1 [length
= 3]
popl %ebx # 38 popsi1 [length = 1]
ret # 39 return_internal [length = 1]
One of the difficulties is that by the time the code gets to the cse1 pass, the
statement "c = a - b" might have been moved below the "a < b" test, making it
harder to optimize. The "bar2" testcase was crafted so this doesn't happen. But
given the need to potentially replace both the sub/cmp insn and the jump insn,
it would be better to move this optimization to combine.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Comment #9 from rask at gcc dot gnu dot org 2007-11-28 18:01 -------
Created an attachment (id=14657)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14657&action=view)
Patch v2 to enhance cse.c
This patch also handles unsigned comparisons and thus optimizes the original
testcase too. Before:
foo:
movl 4(%esp), %edx # 2 *movsi_1/1 [length = 4]
movl 8(%esp), %eax # 3 *movsi_1/1 [length = 4]
movl %edx, %ecx # 35 *movsi_1/1 [length = 2]
subl %eax, %ecx # 7 *subsi_1/1 [length = 2]
cmpl %eax, %edx # 8 *cmpsi_1_insn/1 [length = 2]
jae .L2 # 9 *jcc_1 [length = 2]
addl $100, %ecx # 11 *addsi_1/1 [length = 3]
.L2:
movl %ecx, %eax # 18 *movsi_1/1 [length = 2]
ret # 38 return_internal [length = 1]
After:
foo:
movl 4(%esp), %eax # 2 *movsi_1/1 [length = 4]
subl 8(%esp), %eax # 8 *subsi3_cc_overflow/2 [length = 4]
jae .L2 # 9 *jcc_1 [length = 2]
addl $100, %eax # 11 *addsi_1/1 [length = 3]
.L2:
rep # 39 return_internal_long [length = 1]
ret
I was going to abandon this patch, but maybe it deserves a second chance. :-)
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
------- Comment #10 from steven at gcc dot gnu dot org 2007-11-28 22:02 ------- Are you aware of df_find_def() ? Formatting. IMNSHO, computing DEF-USE chains for this niche optimization loses in the cost/benefit trade-off. The whole patch looks like a hack to me to specifically deal with this particular bug report. You could, of course, show that this is actually a very important optimization... I wonder if you can't just integrate this optimization in cse.c as-is by recording an equivalence "a < b" == "signof(c)" when you process "a - b". In any case, adding this optimization to cse.c is Just Wrong (tm). I don't understand why you didn't even try to optimize this in one of the tree optimizers instead. I thought it was clear GCC is trying to reduce its dependency on RTL optimizations?------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
------- Comment #11 from rask at gcc dot gnu dot org 2007-11-29 00:09 ------- In reply to comment #10 from Steven Bosscher 2007-11-28 22:02: Not until now, and it won't work either, because it uses rtx_equal_p() and the mode of DF_REF_REG() doesn't match that of the REG rtx in the insn. See also <URL:http://gcc.gnu.org/ml/gcc/2007-11/msg00719.html>. The split of the comparison setter and the comparison user across two insns with no link between them is an interesting case of poor infrastructure. Most back ends can't emit the setter before they know what the user looks like and therefore always emit the two back-to-back. At the same time, several passes need to find one from the other but can't rely on them to be back-to-back and because there's no link between them (except if by DEF-USE/USE-DEF), they have to roll their own means of doing so. (So yes, it's been done without DEF-USE before and it can be done without DEF-USE again.) That doesn't catch the unsigned comparison. Actually, how would I even know if it is unsigned or not? There's no way to optimize the signed case with -fwrapv (e.g. Java) at the tree level, because we can't arrange for a - b to be computed in the same instruction as a < b. At the RTL level, it is merely difficult. That makes it less interesting to work on this optimization at the tree level.------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
------- Comment #12 from bonzini at gnu dot org 2007-11-29 11:43 ------- I think this should use find_comparison_args.------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter.
This bug report was submitted for an older version of gcc/g++/gcj. Please recheck with the current gcc-4.3/g++-4.3/gcj-4.3 packages from unstable.
This bug report was submitted for an older version of gcc/g++/gcj. Please recheck with the current gcc-4.3/g++-4.3/gcj-4.3 packages from unstable.
reassign 75773 gcc-4.6 found 75773 4.6.3-4 stop Hi, I could reproduce the bug when compiling with this 4.6.3-4 version (the default in Debian unstable at this time), when using -m32 in amd64:--------------------------------------------------------------------- $ gcc -O2 -S -m32 test1.c -o test1.m32.s $ cat test1.m32.s .file "test1.c" .text .p2align 4,,15 .globl foo .type foo, @function foo: .LFB0: .cfi_startproc movl 4(%esp), %ecx movl 8(%esp), %edx movl %ecx, %eax subl %edx, %eax cmpl %edx, %ecx jae .L2 addl $100, %eax .L2: rep ret .cfi_endproc .LFE0: .size foo, .-foo .ident "GCC: (Debian 4.6.3-4) 4.6.3" .section .note.GNU-stack,"",@progbits --------------------------------------------------------------------- Though surely not important, just for completion, with -m64 the result is completely different: --------------------------------------------------------------------- $ gcc -O2 -S -m64 test1.c -o test1.m64.s $ cat test1.m64.s .file "test1.c" .text .p2align 4,,15 .globl foo .type foo, @function foo: .LFB0: .cfi_startproc movq %rdi, %rax subq %rsi, %rax cmpq %rsi, %rdi leaq 100(%rax), %rdx cmovb %rdx, %rax ret .cfi_endproc .LFE0: .size foo, .-foo .ident "GCC: (Debian 4.6.3-4) 4.6.3" .section .note.GNU-stack,"",@progbits --------------------------------------------------------------------- Also confirmed with GCC 4.7.0, the only difference to the files above is the line about the version of the compiler: --------------------------------------------------------------------- $ gcc-4.7 --version | head -n 1 gcc-4.7 (Debian 4.7.0-6) 4.7.0 $ diff -U0 test1.{,gcc47-}m32.s --- test1.m32.s 2012-05-02 20:05:55.908296453 +0100 +++ test1.gcc47-m32.s 2012-05-02 20:08:01.824292734 +0100 @@ -22 +22 @@ - .ident "GCC: (Debian 4.6.3-4) 4.6.3" + .ident "GCC: (Debian 4.7.0-6) 4.7.0" $ diff -U0 test1.{,gcc47-}m64.s --- test1.m64.s 2012-05-02 20:06:20.652295721 +0100 +++ test1.gcc47-m64.s 2012-05-02 20:07:52.868292996 +0100 @@ -18 +18 @@ - .ident "GCC: (Debian 4.6.3-4) 4.6.3" + .ident "GCC: (Debian 4.7.0-6) 4.7.0" ---------------------------------------------------------------------
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507 Daniel Santos <daniel.santos at pobox dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel.santos at pobox dot | |com--- Comment #13 from Daniel Santos <daniel.santos at pobox dot com> 2012-07-10 10:23:08 UTC --- Well here's another test case for the same problem: extern print_gt(void); extern print_lt(void); extern print_eq(void); void cmp_and_branch(long a, long b) { long diff = a - b; if (diff > 0) { print_gt(); } else if (diff < 0) { print_lt(); } else { print_eq(); } } In this case, the result of the subtraction is directly used in the branch code. However, gcc -O2 -S still generates this output: .file "gcc_cmp_and_branch_test2.c" .text .p2align 4,,15 .globl cmp_and_branch .type cmp_and_branch, @function cmp_and_branch: .LFB0: .cfi_startproc subq %rsi, %rdi cmpq $0, %rdi jg .L5 jne .L6 jmp print_eq .p2align 4,,10 .p2align 3 .L5: jmp print_gt .p2align 4,,10 .p2align 3 .L6: jmp print_lt .cfi_endproc .LFE0: .size cmp_and_branch, .-cmp_and_branch .ident "GCC: (Gentoo 4.7.1) 4.7.1" .section .note.GNU-stack,"",@progbits I'm using Gentoo x86_64: Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.1/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /tmp/portage/sys-devel/gcc-4.7.1/work/gcc-4.7.1/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.1 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.1/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.1 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.1/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.1/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.1/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --with-ppl --with-cloog --disable-ppl-version-check --with-cloog-include=/usr/include/cloog-ppl --enable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --enable-multilib --with-multilib-list=m32,m64 --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.1/python --enable-checking=release --enable-java-awt=gtk --enable-objc-gc --enable-languages=c,c++,java,objc,obj-c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.7.1' Thread model: posix gcc version 4.7.1 (Gentoo 4.7.1) I do hope this can be addressed sometime soon. Thanks.
Sehr geehrte/r Arbeitsuchender, folgender Jobvorschlag ist für alle geeignet, da diese Arbeit ohne besondere Anforderungen auch von zu Hause zu bewerkstelligen ist. Der Arbeitnehmer hat keine Ausgaben und muss keine besonderen Kenntnisse mitbringen. Die benötigte technische Ausrüstung wird von uns frei zur Verfügung gestellt. Zu Ihren Hauptaufgaben gehört das Bücher Einscannen, das Erstellen von Buchwerken, die Datendigitalisierung, die Koordinierung und das Erstellen von Mediatheken. Wir bieten eine attraktive Bezahlung in Höhe von 20€ die Stunde Brutto. Unser Unternehmen verfügt über internationale Zweigstellen auf der ganzen Welt und wir arbeiten im Bereich der Mediendigitalisierung. Zur Zeit sind wir auf der Suche nach neuen Mitarbeitern. Dies müssen Sie mitbringen: Sie verfügen über ein Paar Stunden Zeit am Tag, Sie arbeiten gern von zu Hause, Sie besitzen Flexibilität, Grundkenntnisse von MS-Office sind von Vorteil, sie verfügen über ein Paar Stunden Zeit am Tag und Sie besitzen eine teamorientierte Arbeitsweise. Haben wir Ihr Interesse geweckt? Dann freuen wir uns über Ihre Bewerbung! Senden Sie Ihre kompletten Unterlagen an: JuneNicholsono@gmx.com Wir freuen uns auf Ihre Bewerbung. Mit freundlichen Grüßen Schortis Arbeitsvermittlung
Dear submitter, as the package gcc-4.6 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/796274 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
reopen 75773 reassign 75773 gcc quit The bug still exists in gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2007-11-02 14:17:51 |2018-4-22
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #15 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #16 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #17 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #18 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #19 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #20 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #21 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #22 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #23 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #24 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #25 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #26 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #27 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #28 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #29 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #30 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #31 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #32 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #33 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #34 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #35 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #36 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #37 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #38 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #39 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #40 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #41 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #42 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #43 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #44 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #45 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #46 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #47 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #48 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #49 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #50 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #51 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #52 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #53 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #54 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #55 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #56 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3507--- Comment #57 from owner at bugs dot debian.org --- Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message has not been forwarded to the package maintainers or other interested parties; you should ensure that the developers are aware of the problem you have entered into the system - preferably quoting the Bug reference number, #75773. If you wish to submit further information on this problem, please send it to 75773-quiet@bugs.debian.org. Please do not send mail to owner@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
*你好!* 最近几个月，中国大陆很多医院人满为患，大部分人都发烧咳嗽。根据新唐人记者的采访，有些病人发病的速度极快，三四天时间就会出现高烧和肺部溃烂的情况，甚至很快会死亡。 但是中国医院却统一以流感方式进行处理，官方到底隐瞒了多少疫情的真相呢？ 真相不会永远沉默 正义终究要来临。 详情请看附件。 祝你一切都好！--- *法轮大法是佛法, 是正法。诚念九字真言得福报。* *法轮大法好，真善忍好* 几十年来，在中共的洗脑灌输下，大量的中国人被迫加入了共产党和其附属组织（共青团、少先队）。在「全球退党运动」中，中国人民正在从中共的谎言中觉醒。他们公开声明退出中共，远离邪恶。 此时此刻，我们要让世界听到我们声音: 打倒中共恶魔！结束中共！ 迄今为止, 2024年2月12日 426,111,490 中国民众退出共产党，及其附属组织
*你好!* 牛奶是一种广泛应用于日常饮食的营养饮料。 但对于需要减肥或控制脂肪摄入的人，可选择脱脂牛奶或低脂乳制品；对于儿童、老人和身体不好的人，应选择营养丰富的全脂牛奶或蛋白质、钙含量高的饮料。 不过，有3种牛奶你应该尽量少喝，因为它对你的健康没有好处：保质期牛奶、植物奶、低脂牛奶。 这些信息十分珍贵，请务必查看完整内容！ https://tinyurl.com/niu-nai-zhong-de-ying-yang 祝你和你的家人好运！--- 愿光明与真相同行