https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64696
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114297
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:c0c57246d5b47459bdb488734bc2c004a92668b5
commit r14-9435-gc0c57246d5b47459bdb488734bc2c004a92668b5
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114297
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114238
Haochen Jiang changed:
What|Removed |Added
CC||haochen.jiang at intel dot com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114160
Sam James changed:
What|Removed |Added
Target Milestone|--- |13.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65712
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |MOVED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96564
--- Comment #16 from Richard Biener ---
(In reply to Andrew Macleod from comment #15)
> (In reply to Richard Biener from comment #13)
> > (In reply to Jeffrey A. Law from comment #12)
> > > So I think we could solve this with a bit of help from t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66279
Andrew Pinski changed:
What|Removed |Added
Known to work||4.4.7
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114261
--- Comment #6 from Richard Biener ---
Isn't the "scheduling window" limited somehow? Can we impose an upper bound on
the number of dependences by placing a "virtual barrier" when we hit that
limit?
I don't know the structure of the scheduler o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304
--- Comment #14 from Tobias Burnus ---
Created attachment 57680
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57680&action=edit
Testcase with decimal=COMMA, passes with ifort/ifx/flang - fails with gfortran
> commit r14-9432-g0c179654c31
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114316
Bug ID: 114316
Summary: assert failure with _GLIBCXX_DEBUG and empty range of
singular iterators passed std:: algorithm
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114293
--- Comment #3 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:39737cdf002637c7a652e9c3e36f369cfce581e5
commit r14-9437-g39737cdf002637c7a652e9c3e36f369cfce581e5
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114293
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114316
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114151
--- Comment #19 from Richard Biener ---
So what remains here is differences like
- (chrec = {(long unsigned int) (col_stride_10 * _105), +, (long unsigned int)
col_stride_10}_2)
+ (chrec = (long unsigned int) (int) {(unsigned int) col_stride_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114151
--- Comment #20 from Richard Biener ---
Created attachment 57681
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57681&action=edit
patch for context sensitive range during SCEV
This is the patch I was playing with.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112709
--- Comment #7 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:ad860cc27b3312f9119c7fecb8638a7c1f6d77c9
commit r14-9438-gad860cc27b3312f9119c7fecb8638a7c1f6d77c9
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
--- Comment #22 from Matthias Kretz (Vir) ---
I took your hypot3_scale and reduced latency and throughput. I don't think the
sqrtmax/sqrtmin limits are correct (sqrtmax² * 3 -> infinity).
TYPE Latency Speed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114308
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114310
Richard Biener changed:
What|Removed |Added
Target||aarch64
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114312
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114269
Filip Kastl changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 114269, which changed state.
Bug 114269 Summary: [14 Regression] Multiple 3-6% exec time regressions of
434.zeusmp since r14-9193-ga0b1798042d033
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114269
What|Re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112548
--- Comment #8 from Filip Kastl ---
(In reply to Robin Dapp from comment #7)
> I built executables with and without the commit (-Ofast -march=znver4
> -flto). There is no difference so it must really be something that happens
> with PGO.
> I'd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114316
--- Comment #1 from Jonathan Wakely ---
For a debug mode _Safe_iterator pair __valid_range uses this overload:
template
inline bool
__valid_range(const _Safe_iterator<_Iterator, _Sequence,
_Categ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84318
Jeffrey A. Law changed:
What|Removed |Added
Summary|[11/12/13/14 Regression]|[11/12/13 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84204
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Priori
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113662
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113141
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112815
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113496
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112499
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
--- Comment #3 from Jakub Jelinek -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112709
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
--- Comment #8 from Jakub Jelinek -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111921
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111873
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82894
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Summa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111099
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111592
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110682
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111683
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
--- Comment #11 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110141
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111305
Jakub Jelinek changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111571
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80899
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Resoluti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80491
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Summa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79534
Jeffrey A. Law changed:
What|Removed |Added
Summary|[11/12/13/14 Regression]|[11/12 Regression]
|t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98688
--- Comment #4 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:4aa87b856067d4911de8fb66b3a27659dc75ca6d
commit r14-9439-g4aa87b856067d4911de8fb66b3a27659dc75ca6d
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111224
--- Comment #11 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:4aa87b856067d4911de8fb66b3a27659dc75ca6d
commit r14-9439-g4aa87b856067d4911de8fb66b3a27659dc75ca6d
Author: Nathaniel Shead
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98645
--- Comment #9 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:4aa87b856067d4911de8fb66b3a27659dc75ca6d
commit r14-9439-g4aa87b856067d4911de8fb66b3a27659dc75ca6d
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98645
Nathaniel Shead changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 98645, which changed state.
Bug 98645 Summary: [modules] does not work on PowerPC with IEEE 128-bit long
double
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98645
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98688
Nathaniel Shead changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Assignee|nathan at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 98688, which changed state.
Bug 98688 Summary: [modules] does not work on PowerPC with opaque MMA types
vector_pair/vector_quad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98688
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114317
Bug ID: 114317
Summary: Missing optimization for multiple condition statements
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114121
--- Comment #17 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:73dac51b32575f980289c073969c6d825963d076
commit r14-9440-g73dac51b32575f980289c073969c6d825963d076
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114318
Bug ID: 114318
Summary: Missing Optimization after multiple function calls
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110167
--- Comment #13 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:4c6bb36e88d5c8e510b10d12c01e3461c2aa4259
commit r13-8421-g4c6bb36e88d5c8e510b10d12c01e3461c2aa4259
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114312
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114318
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114317
Richard Biener changed:
What|Removed |Added
Last reconfirmed||2024-03-12
Component|tree-opt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114317
--- Comment #2 from Jan Hubicka ---
> (it would need to elide the stores of course).
We do have way to elide stores, since we can optimize out write-only
values. What we do not have readilly available is the value written to
a reference (ipa-r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114307
--- Comment #4 from Maxim Kuvyrkov ---
What I don't understand is why vect.exp tests run at all for 32-bit ARM
non-neon targets.
All vect.exp are predicated on check_vect_support_and_set_flags, which, as far
as I can tell, has only arm_neon_ok
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112548
--- Comment #9 from Sam James ---
(In reply to Filip Kastl from comment #8)
> I'd like to help but I'm afraid I cannot send you the SPEC binaries with PGO
> applied since SPEC is licensed nor can I give you access to a Zen4 computer.
> I suppose
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114318
--- Comment #2 from Andrew Pinski ---
(In reply to Richard Biener from comment #1)
> That's because main is cold.
Or rather known to be called once which causes the path to be considered cold
unless there is a loop.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99829
Thiago Jung Bauermann changed:
What|Removed |Added
CC||thiago.bauermann at linaro dot
o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99829
Maxim Kuvyrkov changed:
What|Removed |Added
CC||vmakarov at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112652
--- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #4 from Jakub Jelinek ---
> Given that C++ says e.g. in https://eel.is/c++draft/lex.ccon#3.1
> that program is ill-formed if some character lacks encoding in the execution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114313
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114309
--- Comment #11 from M Welinder ---
> Anyway, in GCC's testcase we have:
>
> 9 if (a == 123)
> 10 [[likely]] c = 5; // { dg-warning "both" }
> 11 else
> 12 [[likely]] b = 77;
> Here we have two possible paths, and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114307
--- Comment #5 from Maxim Kuvyrkov ---
Thanks to Christophe L. for explaining the logic behind "is-effective-target
arm_neon_ok".
The issue is that "/* { dg-options "-O3" } */" in pr113576.c overrides
DEFAULT_VECTFLAGS set by check_vect_support
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99829
--- Comment #4 from Vladimir Makarov ---
(In reply to Maxim Kuvyrkov from comment #3)
> Hi Vladimir,
>
> Could you take a look at this, please?
I already got a message from automatic linaro tester yesterday about the new
test failures and looke
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304
--- Comment #15 from Jerry DeLisle ---
(In reply to Tobias Burnus from comment #14)
--- snip ---
> The question is whether the following show give an error as shown above:
> real :: x(3)
> character(len=1) :: s
> ...
> write(99, '(a)') '
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99829
--- Comment #5 from Maxim Kuvyrkov ---
Hi Vladimir,
The email you got from Linaro CI was about tests the ICE changing "names" due
to assert in lra-assigns.cc changing line numbers. E.g.,
FAIL: c-c++-common/torture/vshuf-v16qi.c -O3 -g (interna
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114307
--- Comment #6 from Andrew Pinski ---
The easiest way to fix this testcase is to rename the testcase to O3-pr113576.c
and remove the dg-options
Though we should audit all of the other ones that use dg-options too:
gimplefe-40.c:/* { dg-options
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99829
--- Comment #6 from Thiago Jung Bauermann
---
Created attachment 57683
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57683&action=edit
Preprocessed source file.
I was able to reproduce the ICE on my x86_64 laptop with the following
comma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
Bug ID: 114319
Summary: htobe64-like function is not optimized on 32-bit x86
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
Andrew Pinski changed:
What|Removed |Added
Component|target |middle-end
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112560
--- Comment #6 from Uroš Bizjak ---
v3 patch at [1]
[1] https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647634.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
Andrew Pinski changed:
What|Removed |Added
Known to fail||11.4.0
--- Comment #1 from Andrew Pinsk
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
--- Comment #3 from Pali Rohár ---
For details, here is the compiler which produces the mentioned code:
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114319
--- Comment #4 from Andrew Pinski ---
(In reply to Pali Rohár from comment #3)
> --with-arch-32=i686
This basically causes SSE to be disabled for 32bit by default ...
With the default options to configure GCC, -m32 for x86_64 still enables sse
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110826
--- Comment #3 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:81ee1298b47d3f3b3712ef3f3b2929ca26c4bcd2
commit r14-9442-g81ee1298b47d3f3b3712ef3f3b2929ca26c4bcd2
Author: Harald Anlauf
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111592
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114320
Bug ID: 114320
Summary: New test case in r14-9439-g4aa87b856067d4 fails
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114151
--- Comment #21 from Andrew Macleod ---
(In reply to Richard Biener from comment #19)
>
> While ranger has a range_on_exit API this doesn't work on GENERIC expressions
> as far as I can see but only SSA names but I guess that could be "fixed"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24414
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34038
--- Comment #9 from Andrew Pinski ---
https://gcc.gnu.org/legacy-ml/gcc-patches/2007-08/msg00438.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34038
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33671
Andrew Pinski changed:
What|Removed |Added
CC||janis at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769
--- Comment #6 from Andrew Pinski ---
Created attachment 57684
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57684&action=edit
Testcase from godbolt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36016
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86769
Andrew Pinski changed:
What|Removed |Added
CC||gnu4u at flonatel dot org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83294
--- Comment #9 from Andrew Pinski ---
https://inbox.sourceware.org/gcc-patches/7a5ec7af-fdbf-470f-9414-bf4110331...@ventanamicro.com/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46993
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114001
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61785
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63599
Andrew Pinski changed:
What|Removed |Added
Known to fail||5.1.0, 6.1.0
Keywords|wrong-co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #35 from Eric Gallager ---
(In reply to Дилян Палаузов from comment #34)
> Created attachment 57662 [details]
> Proposed patch
>
> This fixes the problem.
>
> I do not understand the build system to say, that this is the best appro
1 - 100 of 115 matches
Mail list logo