Displaying 20 results from an estimated 2000 matches similar to: "some infos"
2005 Jan 03
9
Just saw your [Asterisk] xJack Segfault in Asterisk
Hi:
Just saw your post while trying to solve a similar asterisk problem. Did
not see any responses. Was your problem solved and what was the solution?
Carey
2007 Jan 05
3
Dovecot's deliver trouble (...probably bug?)
Hello everybody!
I am a Linux admin trying to move my mail
system based on qmail to the software which is more spam-protected:
exim4 + dovecot-1.0rc15 + pgsql . I've downloaded and rebuild dovecot
from src.rpm (for fc4). During
the testing stage I've discovered two troubles:
1) the problem with deliver (...I'm not sure it's a really bug). Here
is relevant part
of my
2017 Jan 26
2
Critical XRay fixes for Arm32
I see. Thanks for clarifying.
I'm Ok with merging these if Dean agrees, as I believe he's the code owner.
Thanks,
Hans
On Thu, Jan 26, 2017 at 11:47 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> There were no LLVM tests for presence of XRay instrumentation map in the
> emitted assembly. You can see that https://reviews.llvm.org/D28624 adds this
> check to the
2017 Jan 26
2
Critical XRay fixes for Arm32
I'm wondering why the lit tests didn't catch this as part of testing rc1 on ARM.
On Thu, Jan 26, 2017 at 11:25 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> XRay is tested automatically on build-bots with tests in LLVM and
> compiler-rt . Or are you asking for manual testing instructions?
> Of these 2 patches, the compiler-rt patch depends on LLVM patch because
2017 Jan 26
2
Critical XRay fixes for Arm32
How is XRay tested? IIRC, Renato didn't see any test failures on ARM?
Merging sounds reasonbaly, I'd just like to understand what's the risk
for the branch.
On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> Hans, these changes reached trunk in https://reviews.llvm.org/rL292516 and
> https://reviews.llvm.org/rL292517 . Could you look?
2017 Jan 26
2
Critical XRay fixes for Arm32
Sorry, I initially included LLVM-Commits rather than LLVM-Dev. Fixed.
On 26 January 2017 at 03:26, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> Hi Dean, Renato,
>
> AFAIK, unfortunately, these critical Arm32 XRay fixes are not yet in 4.0:
> https://reviews.llvm.org/D28624 , https://reviews.llvm.org/D28623 . The
> first repairs XRay instrumentation map emission.
2001 Feb 16
1
error_2_can't_find_apps
Hello,
I tried lunch something but the anwer was
"can't find apps"
(I used absolute path too)
[serge@rex wineserver-rex]$ wine
/windows/ProgramFiles/Office/winword.exe
Invoking /opt/wine/bin/wine.bin /windows/ProgramFiles/Office/winword.exe
...
Wine failed with return code 2
/usr/bin/wine: line 516: 1046 Compl?t? tail -f $log_name
Deleting /tmp/wine.log.Vv4t6C
2007 Dec 14
1
Quadratic Programming
Hi all!
I have a little question concerning quadprog. To make it simple I'll start by stating the problem:
I want to minimize
h(d,delta)=0.5d^T B d +nabla(f(x))^T d +rho*delta^2
With respect to d\in R^n and delta \in R. I obviously have constraints (depending on both d and delta).
Solve.QP does give me a good result for d but I cannot obtain anything for delta. Simce dim(Dmat)=n and
2017 Jan 09
2
Removed a call to EmitXRayTable() from ARMAsmPrinter
Sharing with the mailing list... Please, see below.
On 9 January 2017 at 23:45, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> Hi Dean,
>
> I have seen that you removed the following code from ARMAsmPrinter.cpp in
> revision 290858:
> // Emit the XRay table for this function.
> EmitXRayTable();
>
> Was this done by mistake or on purpose?
>
> Without
2016 Aug 05
2
XRay: Demo on x86_64/Linux almost done; some questions.
Hi Dean,
I have a question for 32-bit platforms. I see in the code that you used the
following in compiler-rt/trunk/lib/xray/xray_interface_internal.h :
struct XRaySledEntry {
uint64_t Address;
uint64_t Function;
unsigned char Kind;
unsigned char AlwaysInstrument;
unsigned char Padding[14]; // Need 32 bytes
};
And the peer code in llvm/trunk/lib/Target/X86/X86MCInstLower.cpp :
void
2017 Jan 09
2
Removed a call to EmitXRayTable() from ARMAsmPrinter
Hi Renato,
As far as I understand, such issues should be caught by the tests in compiler-rt/test/xray/TestCases/Linux.
I found the following lines in compiler-rt/test/xray/lit.cfg that seem to disable the tests for non-64-bit targets:
if config.host_os not in ['Linux'] or config.host_arch.find('64') == -1:
config.unsupported = True
@Serge: You will need to change this
2001 Oct 02
2
AFS and tokenforwarding
For some reasons the afs tokenforwarding stuff has changed
siginificantly from v 2.9p2 to 2.9.9p2.
This makes it impossible to use public key authenticication in a
standart AFS environment.
I don't know the reasons for these changes.
In any case attached is a patch which restores the old behaviour.
Regards
Serge
--
Serge Droz
Paul Scherrer Institut mailto:serge.droz at
2017 Jan 26
2
Critical XRay fixes for Arm32
On 26 January 2017 at 20:04, Serge Rogatch <serge.rogatch at gmail.com> wrote:
> Thank you for considering.
> Dean, Renato - what do you think?
Hi, sorry it took so long. Yes, those two patches are fundamental to
make XRay work on ARM. Backporting makes sense.
We already added XRay on both ARM and AArch64 release notes, so they
have to work. :)
--renato
2016 Aug 22
2
XRay: Demo on x86_64/Linux almost done; some questions.
Hi Dean,
Do you have any estimates on when https://reviews.llvm.org/D21982 will
reach mainline? (As I understood it's not yet there, looking at
http://llvm.org/svn/llvm-project/compiler-rt/trunk ). I would like to test
ARM port of XRay, so ready logging would be handful.
Thanks,
Serge
On 8 August 2016 at 17:41, Dean Michael Berris <dean.berris at gmail.com>
wrote:
>
> > On 8
2014 Dec 11
2
[LLVMdev] Debugging on unavailable hardware
Hi Renato,
Thank you very much for the directions, I am going to recommit my fix.
What are hardware used in buildbots? Are these common boards like
PandaBoard or some thing special? What is RAM installed?
Thanks,
--Serge
2014-12-11 2:36 GMT+06:00 Renato Golin <renato.golin at linaro.org>:
> On 10 December 2014 at 19:06, Serge Pavlov <sepavloff at gmail.com> wrote:
> > In
2007 Dec 06
1
Solve.QP
Hi there,
I have a major problem (major for me that is) with solve.QP and I'm new at this. You see, to solve my quadratic program I need to have the lagrange multipliers after each iteration. Solve.QP gives me the solution, the unconstrained solution aswell as the optimal value. Does anybody have an idea for how I could extract the multipliers?
Thanx,
Serge
"Beatus qui prodest quibus
2007 Dec 05
1
Quadratic programming
Hi,
I'm quite new at R and I haven't found the answer to my question anywhere on the net, so either it is trivial or not documented. So, bare with be.
I am using the quadprog package and its solve.QP routine to solve and quadratic programming problem with inconsistent constraints, which obviously doesn't work since the constraint matrix doesn't have full rank. A way to solve this
2001 Feb 16
1
different_languages_problem
Hi,
what to do with this?
thanks in advance
[serge@rex serge]$ wine write.exe
Invoking /opt/wine/bin/wine.bin write.exe ...
For language 'fr' several language ids were found:
fr_FR - 040C; fr_BE - 080C; fr_CA - 0C0C; fr_CH - 100C; fr_LU - 140C;
Instead of using first in the list, suggest to define
your LANG environment variable like this: LANG=fr_FR
Wine exited with a successful status
2016 Aug 04
2
XRay: Demo on x86_64/Linux almost done; some questions.
> On 4 Aug 2016, at 06:27, Serge Rogatch <serge.rogatch at gmail.com> wrote:
>
> Hi Dean,
>
> I have a question about the following piece of code in compiler-rt/trunk/lib/xray/xray_trampoline_x86.S :
> movq _ZN6__xray19XRayPatchedFunctionE(%rip), %rax
> testq %rax, %rax
> je .Ltmp0
>
> // assume that %r10d has the function id.
> movl %r10d,
2014 Apr 06
2
[LLVMdev] [cfe-dev] Code reviews now at http://reviews.llvm.org
Files '.arcconfig' still contain reference to
http://llvm-reviews.chandlerc.com/, so arcanist doesn't work.
Thanks,
--Serge
2014-04-06 3:11 GMT+07:00 Manuel Klimek <klimek at google.com>:
> On Sat, Apr 5, 2014 at 8:42 PM, Manuel Klimek <klimek at google.com> wrote:
>
>> Short update - the sending to the *-commits lists doesn't work yet - I'm
>>