Age | Commit message (Collapse) | Author |
|
Change-Id: I34e9a98586b795a3fa31ae775aee7898b36e65d4
|
|
Change-Id: I6a3f8c9bffd2dbac90c73e472f99dd97b9977127
|
|
*bzzt*, <lightning arcs, faint smell of ozone>, it's alive!
Change-Id: I0b42f4e2603e6d76200d63ab2e26bbb856ae1173
|
|
Change-Id: I1e253922fdb606648eff9865f1125a24e35b0d9a
|
|
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01145.html
http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01147.html
now we just fail instead of crash
Change-Id: I329c676337885bcf4fdfdcdb5912d75424862126
|
|
ELFv2 ABI on ppc64 optimises stack allocation
(http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01149.html
so we're getting no argument save area
This now appears to pass the simple cases and onwards
to the tricky ones
Change-Id: Ie56d148ebea7fcfc023cb7183bc97f09186e66b4
|
|
Change-Id: Id3928ef5ac68ea13a7aa8723bc8b068ecf8075a0
|
|
Change-Id: Icc386083ecd9faefbedebbb9d2496a4eddfa0b2b
|
|
almost certainly won't get us too far, but a start
Change-Id: Ic20b97a97b6d506c32322173bd8332d15c3a4555
|
|
in the absence of any other constructors, the compiler will automatically
generate a public no-arg constructor
Change-Id: I70eca507cd8e16e33580b3398d41d70690bc2909
|
|
Change-Id: Ia99765a6226317ee41ffb02a1b0dd7e6fd944a90
|
|
Change-Id: Icef19ef61ee0af2dd3bda527263934006271f219
|
|
Change-Id: If4fff3dd37326fbcdd01b743355a16591d71fa69
|
|
Change-Id: Ia8befb8d69914ce971174fc5f2ffc0e2f506a940
|
|
Change-Id: Ie41d6b0170a035a694dd270c311a137fd1810e74
|
|
Change-Id: I05c907a38b562231e968c17f14e09ef80e0a6ed1
|
|
Change-Id: Ide34abab9417b849ea58aafab386e13e67d240be
|
|
found by UCDetector
Change-Id: I7f97e15667159cf8ee776e8f32fdcdec8ec00ed6
|
|
Change-Id: I086964c6f6ce52c60c52b6dbc445d3c21d22c80a
|
|
.. actually thrown
Change-Id: Ia326ac7f82e11b948ed0f34e20908a96e7adcd10
|
|
Change-Id: Ibeeefc6e6ee8f7bed97a02f569f239ff035d38c4
|
|
Change-Id: I25fef9590a34ec8d9aab182b3d267ae3cd649a87
|
|
Change-Id: I064c738b371999bb73726bde3669c710742fae80
|
|
Change-Id: I9889e97a7f9e70d8b2d82e26d9e0f971a943d007
|
|
...though only on gcc3_linux_x86-64 for now.
Change-Id: Id90554425e78b38a5a97149f2a7d3ac04cbe0c9b
|
|
Change-Id: Ie5608777b0bee002437117709d2c96062a39ff55
|
|
Change-Id: I44e2043e5da23bc9421c03e550ef1d8b7ebaad36
|
|
Change-Id: I6c93864f501f646a8940eac221a88c87b3f75525
|
|
Change-Id: Id9f30938f594cb6fe73bf40adfffa65ec1b42cd1
|
|
Change-Id: Iad6a0e5e04dd899827f7dc5dcdbde360ce34716d
|
|
Find "missing headers," where a function is declared directly in the
.cxx (as extern) and not defined, and should arguably instead be declared
in an include file.
Change-Id: I6d83ee432b2ab0cd050aec2b27c3658d32ac02a2
|
|
Change-Id: I5703b269380bbaefd503780b8d396552e6517ddc
|
|
...as passing (an upper bound on) the number of vector registers used in %al is
only required for variable-argument function calls, according to
<http://www.x86-64.org/documentation/abi.pdf> "System V Application Binary
Interface: AMD64 Architecture Processor Supplement, Draft Version 0.99.6."
Unclear why this got added in f424e55b4e66ffbee5b34f45ef5ea18d77c4d15c
"INTEGRATION: CWS sixtyfour11," maybe on the basis of "doesn't hurt."
Change-Id: If6f8359d5bf6458274905d64adf82634bf90a24d
|
|
Change-Id: I60026ccc9c752389260a6b4e6255c53981eea4ba
|
|
Change-Id: I9a812220b58cf6da00d854e65794f7c673ab239d
|
|
Thanks to Dagobert Michelsen for noticing.
Change-Id: Ife333e74c145ad71c451cb60ba9a8ee4222a2183
|
|
Change-Id: Ic301459b751585a91aa4d6667fbe512d13bbb458
|
|
Change-Id: Ib51b05eb3f7c5d1288bee0f9f738ab1f37251c3e
Reviewed-on: https://gerrit.libreoffice.org/9722
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
|
|
Change-Id: I5863de6d8b1f0fe2419ea7419b1ff90087bb513d
Reviewed-on: https://gerrit.libreoffice.org/9715
Tested-by: Michael Stahl <mstahl@redhat.com>
Reviewed-by: Michael Stahl <mstahl@redhat.com>
|
|
Change-Id: I2daafd711aedab17b6c13fde95c8af5f49d38a7c
|
|
when throwing exceptions
Change-Id: I6edfb6b6745499f802b0e3c0e096a36fb7c32aac
|
|
Change-Id: I8ad64babd43c2a692c305f3fa56331edb6d502ee
|
|
Now that we have default values for Exception constructor params,
remove lots of boilerplate code.
Change-Id: I620bd641eecfed38e6123873b3b94aaf47922e74
|
|
same as 08947735f9cc4b7bd69676c9dd4d1700e8e3b15b for gcc_linux_x86-64
Change-Id: I28d138dd13adc9a3e09d46befe69ac86ab1fffb6
|
|
Detect arguments larger than 64 chars passed by value.
Change-Id: I9b0ea9ccb99d115984a26eab67c9cf6afd5f6cae
Signed-off-by: Stephan Bergmann <sbergman@redhat.com>
|
|
Change-Id: Id2c15eba3f70cd8f1ae8869bc0838aef13cd96ee
|
|
Change-Id: Ia37b21af217af9b24522da28e817b4cb6ca2f8c9
|
|
Change-Id: I3e51a62710bb46c8255fd228d41d9300c90a1fb5
Reviewed-on: https://gerrit.libreoffice.org/9360
Reviewed-by: Thomas Arnhold <thomas@arnhold.org>
Tested-by: Thomas Arnhold <thomas@arnhold.org>
|
|
This reverts commit 9ab99483808bad973363f1f27bb548c8628ace1d. Coverity warning
about mkstemp without umask appears to be bogus (cf.
<https://communities.coverity.com/message/6516> "Why are uses of mkstemp
'without securely setting umask first' being flagged?) and calling umask is not
MT-safe, see fdo#60338 "FILESAVE: Saved files have incorrect permissions on
linux."
|
|
...as it needs a JNIEnv passed in, so cannot use the dtor directly. Maybe this
code clarification helps silence Coverity's false resource leak reports.
Change-Id: I32e043e3fa9097263302a6c639e6815512410f4e
|